ID: 11618 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Analyzed +Status: Closed Bug Type: Documentation problem Operating System: linux 2.2.16-22 PHP Version: 4.0.4 New Comment:
Sorry, but the bug system is not the appropriate forum for asking support questions. Your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php Thank you for your interest in PHP. The manual now contains clear exmaples of headers that should be sent to prevent caching of both HTTP/1.0 and HTTP/1.1 connections. Previous Comments: ------------------------------------------------------------------------ [2002-02-08 08:33:13] [EMAIL PROTECTED] Ok. Try telnetting to that page "telnet yoursite.com 80" Type: HEAD /thepage.php HTTP/1.1 Host: yoursite.com Obviously replace thepage.php and yoursite.com with your actual site. See what the headers are (especially the "Pragma:" or "Cache-Control" headers) ------------------------------------------------------------------------ [2002-02-07 22:41:59] [EMAIL PROTECTED] To answer the most recent question from alindeman (I apologize, but I do not know your name): The mention of nocache isn't exactly just HTTP/1.0, however the Pragma header in fact is unique to HTTP/1.0 and was only included in HTTP/1.1 to maintain backwards compatibility. No directives exist for this header except nocache. HTTP/1.1 introduces the Cache-Control header, and with it comes many available directives. In fact, nocache is still one of these. I'm honestly not sure how the session_cache_limiter is implemented at the protocol level, but I can try to figure it out if it would be helpful to you. guo_feng: Though from your brief account I would say that you have now chosen the most appropriate value for session_cache_limiter (assuming it affects the value of the Cache-Control header), I would suggest learning more about it so that you feel more confident in your implementation. To briefly answer your question, however, public basically declares that the content may be cached by anything. Private has a bit more unclear definition to me (you might find more clarification in your research), but it basically allows caching but not in a shared cache. An example of a shared cache would be a proxy that many people are connected to, so the content might be considered a bit too sensitive to be accidentally returned to another user. Hope that helps. Thanks for all your help guo_feng. Chris ------------------------------------------------------------------------ [2002-02-07 19:33:35] [EMAIL PROTECTED] Wasn't "nocache" a HTTP/1.0 thing? Is "must-revalidate" the HTTP/1.1 equivilant? Can anybody verify this so that I can do something with the docs. ------------------------------------------------------------------------ [2001-06-23 06:35:20] [EMAIL PROTECTED] reclassified as documentation problem. This should be explained better in the manual. ------------------------------------------------------------------------ [2001-06-22 12:57:37] [EMAIL PROTECTED] I have solve the problem when I set session.cache_limiter =must-revalidate But I don't why!Can somebody tell me? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/11618 -- Edit this bug report at http://bugs.php.net/?id=11618&edit=1 -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
