503 instead of 404 -> Caching problem
Peter Zechmeister <[email protected]>
| Newsgroups | gmane.comp.cms.zms.devel |
|---|---|
| Message-ID | <[email protected]> |
Hello, when requesting an URL which does not exist (i.e. http://www.myzms.at/e1/e2/e999999999 ZMS/Zope sends an 503 (Service Unavailable) Error. But it should be an 404 (Not Found) Error. This causes problems with our accelerating cache (Squid). When a page moves. I.e. from www.myzms.at/e1/e2/e3 to www.myzms.at/e1/e20/e3 , ZMS/Zope then delivers an 503 for the old Url and Squid thinks service is unavailable and will probably come back in some time. So Squid delivers this cached page on and on. Even if someone does a "Force Reload" on this page (which shows an Error Page with Code 503 indeed, but does not impress Squid). So I think a 404 instead of a 503 would solve this, because Squid knows then, that this place does not exist any more. Regards PZ -- "Ordnung ist für einfach denkende Menschen das Ergebnis der ordnenden Tätigkeit eines ordnenden Wesens.", Hayek