Last modified: 2005-10-24 10:03:01 UTC
In the week or so I've been unable to make any new pages with IE (prior to that it was fine). Every time I try, I
get "HTTP Error: Resource is not found". I can still create pages OK with Safari and Mozilla, but I don't always
have access to them. Editing existing pages with IE seems to be fine. It's got me stumped - anyone got any
idea what's going on? (I haven't changed my preferences at all, so it's unlikely to be anything to do with that).
No new pages, templates, categories, redirects...nothing. Several other Wikipedia users have reported the
same thing (see the URL listed above).
Same issue. This is not an issue it IE or Microsoft, as some MAC users have
complained. I also get the same error using Perl. Were the headers recently
changed to send a 404 on a GET request when the page does not exist? Example:
tomg added the 404 return code recently; this has been periodically discussed on the
tech lists but never got done.
A browser should still be showing the edit form with no problem. James, I haven't been
able to reproduce this problem with IE 5.2.3 on Mac OS X 10.4.2 or with IE 5.0 in
Classic. Can you check with 5.2.3 and confirm that it's still there?
I'm not convinced that 404 should be returned on *edit forms*, though it would make
sense on page *views* of nonexistent pages. But it shouldn't actually stop anything
from working that's not itself badly broken.
Can't comment on 5.2.3, but it's definitely still a problem in 5.2.1.
Can you please try 5.2.3 to check if it's a bug in 5.2.1 or perhaps some other problem?
It doesn't seem to work in 5.2.3 either.
The same issue I mentioned above while using GET for non-existant pages has also
been reported on Bugzilla:3731. This is using PERL, we do not receive the error
while using POST with &action=edit, just GET. Firefox ignores the 404 header as
it assumes the content is the 404 page, and I believe you can turn off "Show
friendly HTTP errors" in IE to bypass it. But when reading the header only Perl
just see's the 404. Do we need this header to be sent?
I have no idea why you're seeing an error, this should work fine under all
I've gone ahead and reverted the change, though.
*** Bug 3731 has been marked as a duplicate of this bug. ***
Works fine now, by the looks of it. Don't know what you did, but thanks for doing it!