Think the IE issue might be with small custom 404 pages: "As this page is less than 512 bytes in size, the Toolbar (and Internet Explorer, for that matter) will display an internal 404 page instead." http://www.google.com/support/forum/p/Webmasters/thread?tid=4ab6a12fada20e0d&hl=en
As things are, without the custom error page, I don't get an error page at all in FF 3.0.7 or Galeon or Opera. I just get "invalid function" . That's a great way to lose users. Some of them will hit back but a lot won't. And they won't be able to send an email or do anything to help fix the problem. http://codex.wordpress.org/Creating_an_Error_404_Page has a nice listing of the error codes and a way to return an explanation. Other people use keywords in the URL to suggest possible pages. Which is neat. When my coding skills are up to it, I'll change web2py to support custom error pages so that Google and users get what they need. I feel that strongly about it. On Mar 12, 9:19 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > routes_onerror was designed to catch errors (like 400, 404, etc.) not > return a standard page instead of an an error page. It returns 303 to > redirect to the customizable page. This was done on purpose because > some browsers (IE for example) do not display the content of a page > if the page status shows an http error. > > I think the correct behavior is correct. > Anyway, this issue is open for discussion and I'd like to her more > opinions on the topic. > > Massimo > > On Mar 12, 10:51 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > Let me look into this. > > > Massimo > > > On Mar 12, 5:35 pm, Jim <jdeib...@gmail.com> wrote: > > > > Saw how to add a custom error message in this > > > thread:http://groups.google.com/group/web2py/browse_thread/thread/834cbe2539... > > > > That's what I want to do but if I use routes_onerror it returns 303: > > > > 127.0.0.1, 2009-03-12 13:30:55, GET, /myapp/default/BAD-URL, HTTP/1.1, > > > 303, 0.183876 > > > > Google and other spiders will want an unambiguous 400 or 404. > > > >http://googlewebmastercentral.blogspot.com/2008/08/farewell-to-soft-4... > > > > You can see 404s via the Google webmaster > > > tools:http://googlewebmastercentral.blogspot.com/2008/10/webmaster-tools-sh... > > > > I've turned this off for now but it would be nice to get a "hard 404" > > > for URLs that don't work. > > > >http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html > > > > 303 See Other > > > > The response to the request can be found under a different URI and > > > SHOULD be retrieved using a GET method on that resource. This method > > > exists primarily to allow the output of a POST-activated script to > > > redirect the user agent to a selected resource. The new URI is not a > > > substitute reference for the originally requested resource. The 303 > > > response MUST NOT be cached, but the response to the second > > > (redirected) request might be cacheable. > > > > The different URI SHOULD be given by the Location field in the > > > response. Unless the request method was HEAD, the entity of the > > > response SHOULD contain a short hypertext note with a hyperlink to the > > > new URI(s). > > > > Note: Many pre-HTTP/1.1 user agents do not understand the 303 > > > status. When interoperability with such clients is a concern, > > > the > > > 302 status code may be used instead, since most user agents > > > react > > > to a 302 response as described here for 303. > > > > 400 Bad Request > > > > The request could not be understood by the server due to malformed > > > syntax. The client SHOULD NOT repeat the request without > > > modifications. > > > > 404 Not Found > > > > The server has not found anything matching the Request-URI. No > > > indication is given of whether the condition is temporary or > > > permanent. The 410 (Gone) status code SHOULD be used if the server > > > knows, through some internally configurable mechanism, that an old > > > resource is permanently unavailable and has no forwarding address. > > > This status code is commonly used when the server does not wish to > > > reveal exactly why the request has been refused, or when no other > > > response is applicable. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
