Breaking Code Elements cached
Bengt Giger <[email protected]>
| Newsgroups | gmane.comp.web.zope.silva.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi this is a issue with Silva 1.1, and I'm not shure if this was fixed in the mean time: If a code element fails, the page will be displayed with a message like this instead of the desired output: [external source element is broken] error message: content The error gets trapped completely by Silva. The problem: this page will be delivered like every other correct page. After all it will be *cached* in HTTP caches like every other correct page. Even if the error is fixed, clients will still see the error because they rely on the cached page, as long as their copy is not expired. Therefore Silva must indicate that this page could not be assembled as desired. I suggest that the Code Element class sets the reponse header to 400 (Bad Request), this will avoid any HTTP caching. Regards Bengt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQEVAwUBQnIqYRxwykL/U8y3AQKBbQf+O/wmX83d2W5yopQBmaR4IEenpIdxW9Ek ieO6tzqUZtht8SEl+CQuagt1BmsY6BvGbdUXQvPWmQ9ELqa6Xl+mJNFalxFBcvNT byGf0U864clA258+Hwf3Mb/SW6yiR9Anay4xiE5wLDKhBmxsr7p6hLU0xQJVxic9 46E9vi/xoW9NvUTU01Qsxr+m6rRFdnousV0iGN9EB3sB1zxpxBE5WeShUKvqRz1G vQyRYjAFD5vlJTVrbEKyKQ54SzeJhynj/pkcDiSwT8aNngFWvrMpGAiUqbp75lJx tRwvu+pDeLrwWqOCV0rkDCSW3T6iPfOEcYa7DnAziuzAT6S0AYhyqQ== =PcSX -----END PGP SIGNATURE-----