On Wed, Apr 13, 2011 at 6:41 AM, Yuka Poppe <y...@xs4all.nl> wrote: > I noticed this myself a while back; It was'nt django specific, and I dont > know about IE, I generally try to avoid using that; But in case of Chrome, > whenever it encounters a 404 error (or certain other conditions) it seems to > decide the visitor is better off being served a generic google > designed/generated status report about whats happening on the page then one > authored by the webserver/webapp itself.
It actually has to do with the length (in bytes) of the 404 page. Certain browsers -- some versions of IE, and Chrome -- detect "short" 404 pages and substitute the browser's 404 page instead. I believe that the cutoff is 512 bytes, but you may want to test in different browsers to be sure. To fix it, you'll just have to pad your 404 page; this is why you'll sometimes see something like:: <!-- aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa --> In the source for 404 pages. Jacob -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
