Error 404 when reading blog from some places

  • Unknown's avatar

    Hi all,

    One of my friends hosts blog here at http://ladyvera.wordpress.com.

    I can read this blog correctly when browsing from my company proxy (which is in Ireland), but from my home in Denmark I get “404 error” for all articles past May 4th, 2006.

    If I try to browse from home using anonymous proxy, all works.

    Can you help here? I see this as a problem in your hosting, but this problem shows only in very rare conditions.

    I am directly connected to internet and without any proxy.

    Please help!

  • Unknown's avatar

    Is the 404 error displayed or wrapped within his or her theme or is it a browser error page?

    Care to give specific examples of posts that aren’t coming up for you? I just brought up a number of posts labeled after May 4th and they come up fine here. (edit: I can view every post from May 1st onwards)

    Sounds more like a connection issue on your end if you can view it sometimes but not others.

  • Unknown's avatar

    The error is wrapped in the browser:
    http://donangel.wordpress.com/files/2006/05/vera_error.PNG

    Certanly it could be an issue with the internet provider, but I do not believe so, since the error is output by WordPress, i.e. it receives somehow weird request.

    If you want to track this down, you can enable errors logging for her blog and track down the requests, coming from the same IP, from which this forum posting came. It should help…

    Please, do not hesitate to contact me at public AT doncho DOT net, I am eager to resolve that issue, since I feel part of the guilt (because I convinced her to migrate to this service, ermmm…)

    Thanks!
    Doncho

  • Unknown's avatar

    Thanks for the pic. :)

    It’s strange actually as I can see the Posts fine. (Seems like with foreign characters causing an issue with the URL, it’s more of a all or nothing problem. We all do see it or we all don’t see it.)

    I’ve gone ahead and sent in a feedback to staff with a pointer to this thread. Lets see if we can flag someone down on this one.

    Hope this helps,
    -drmike

  • Unknown's avatar

    I just saw that the same problem exists with another (also cyrillic) blog:
    http://monito.wordpress.com

    If you try to see the post
    http://monito.wordpress.com/2006/05/24/%d0%bc%d0%b8%d0%bb%d0%b0-%d0%bc%d0%b8-%d0%95%d0%bb%d0%b5%d0%be%d0%bd%d0%be%d1%80%d0%ba%d0%b5/
    it does not work. However, the post is there. But you cannot read and comment.

  • Unknown's avatar

    this (and other) link ‘works for me’.

    make sure your browser does encode international URLs with UTF-8 and correctly determine page encoding (should be UTF-8 as well).

  • Unknown's avatar

    Works for me as well in IE 6.0.

  • Unknown's avatar

    As you can see, the browser is the latest version of FFox.

    What I think happens is rare to repro bug in WP (or the hosting server) handling of this URLs when they come from this referer. I clearly understand it sounds like “magic”, but unfortunately that’s how it behaves…

  • Unknown's avatar

    Hi again,

    After some silence here, I continue to dig and have some more infromation for you:

    It does not work not only for this blog, but also for all blogs in Cyrillic, and so far in Macedonian.

    It seems the problem is hidden somewhere in the modrewrite, which screws up the things, unfortunately only for my address (since no one complains yet).

    I would like to ask the support: is there a way for a blog owner to turn off the need of “modrewrite”, i.e. their blog posts to be addressed by ?p=<post number> manner? I am sure that would resolve the issue.

    I am also almost sure that the problem raises mainly when you access your site without a proxy. modrewrite seems to work well, if the request is done via proxy server, but fails (frequently for me), if the request is done directly by the browser. Can you test ?

  • Unknown's avatar

    Best bet would be to send in another Feedback from your Dashboard with a pointer to this thread along with a reminder that this has been an ongoing issue for some time. It appears that, as you state, Cyrillic-characters appear to be causing an issue somewhere. (I’m leaning more towards a database/charset issue but it may be with htaccess as you suggest)

  • Unknown's avatar

    The problem also occurs with posts having Greek characters in their title. It seems that firefox does not handle consistently long urls (created automatically when a post has a title in a non-latin charset language). A quick fix is to change the post-slug of the posts having this problem.

  • Unknown's avatar

    Agreed, but you shouldn’t have to be doing that. I know a lot of the search results that I get come from the works within the URL/ slug.

    Unless, of course, Firefox can’t support Greek characters.

  • Unknown's avatar

    It isn’t necessarily anything to do with the greek. Greek characters aren’t foreign; nor are Cyrillic. It happens with blogs in Roman characters on wordpress.
    As with the examples given above, the problem has always been fixed for me by refreshing the browser.

  • Unknown's avatar

    It could be a problem with firefox sending a malformed GET request to LiteSpeed when URLS are too long. Or it could be a bug of LiteSpeed. Unfortunately the problem is not always reproducible as it happens randomly.

    A fix from WP’s side could be an option to generate post-slug entries based on something else than the post’s title (e.g. the post date).

  • Unknown's avatar

    A fix from WP’s side could be an option to generate post-slug entries based on something else than the post’s title

    That’s hard coded into the code. They would have to change that for everybody. And, from looking at the number of blogs that run WordPress and almost all of them have that feature turned on, I don’t think it would go over well.

  • Unknown's avatar

    drmike, I totally agree that it’s “hard-coded ” and it’s in wp-config.php. However, it could be possible to make that an option without much hassle…

  • Unknown's avatar

    I totally agree that it’s “hard-coded ” and it’s in wp-config.php.

    Actually that’s for the standard WordPress. They’re running a different codebase here for WP.com.

  • Unknown's avatar

    They’re running a different codebase here for WP.com.

    …which is another reason to implement as many user-specific setup variants as possible.
    It’s easily doable (I have enough PHP development knowledge to say that), the question is only if they are willing to do it:
    * New checkbox in “Options”
    * New “warning” when a user changes that option (before Apply in Options)
    * One more record in options’ table
    * Some additonal processing in the links generation code!

  • Unknown's avatar

    which is another reason to implement as many user-specific setup variants as possible.

    You may want to follow that URL I suggested. You may be missing the point of the software. :)

  • Unknown's avatar

    To put some emphasis to the frustration of this problem please refer to this thread. In a multiuser blog I administer, some non-techie authors usually forget to change the post-slug and publish their posts resulting to very long urls (since their post title is in Greek).

    As mentioned in the thread, the problem is with rss readers (and rss aggregators) that cache the old-long-non-working url resulting to 404 even if the post-slug has been changed after a post has been published.

    Just my 2c in an effort to convince you to consider this as an important issue since it keeps away from WP a number of future non-english bloggers.

  • The topic ‘Error 404 when reading blog from some places’ is closed to new replies.