ID: 5415 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Closed Bug Type: Session related Operating System: Linux 2.2.15 PHP Version: 4.0.1pl2 New Comment:
I'm quite sure that it's not okay. "private" does not mean that no caching should take place, instead it means caching is only okay for the client, not any proxies. If caching was to be prevented, then I must say that the Cache-Control header would be incorrect, since then it would have to be Cache-Control: private, max-age=0, pre-check=0 Instead, the Cache-Control header allows caching for 1 hour (3600 seconds) while the Expires header prevents caching by using a long-ago date. So, you must admit that, should you be right, the Cache-Control header was broken, and should [EMAIL PROTECTED] and I be right, the Expires header was broken. How ever you look at it: these headers don't go together. However, in my opinion, the Cache-Control in the example is correct, while the Expires header should have a date 60 minutes from when the header was written. Previous Comments: ------------------------------------------------------------------------ [2000-07-07 10:09:23] [EMAIL PROTECTED] That's OK, that's to prevent caching. Please, if you aren't sure it is a bug or not, ask on the list, do not submit bug report. Bug report is for something you sure is a bug. ------------------------------------------------------------------------ [2000-07-06 21:12:52] [EMAIL PROTECTED] This bug is valid for configurations where session.use_cookies=1. When session.cache_limiter=public my session featured PHP pages send correct HTTP headers, but when I set the previous mentioned parameter to ''private'' strange things happend... This is normal: Expires: Wed, 5 Jul 2000 20:15:44 GMT Cache-Control: public, max-age=3600 But what is this?!: Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: private, max-age=3600, pre-check=3600 ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=5415&edit=1
