#18897 [Fbk->NoF]: Erroneous 404 and others cache-unfriendly headers

ID: 18897 Updated by: sniper@php.net Reported By: om_phpnetbug028@olden.ch -Status: Feedback +Status: No Feedback Bug Type: Website problem Operating System: any PHP Version: 4CVS-2002-08-13 New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. Previous Comments: ------------------------------------------------------------------------ [2003-01-03 07:59:37] goba@php.net OK, so I have added the last-modified header now, and removed the cache control header. Vary: Cookie is not for nothing there. We have a cookie which do affects the display of manual pages, and we will introduce another cookie probably in the future (you'll be informed). The errorneous 404 is already corrected by Sander. So please check if there is still any problem with the pages... ------------------------------------------------------------------------ [2003-01-02 20:06:45] nicos@php.net Is it still an issue? Thank for your report. ------------------------------------------------------------------------ [2002-11-18 03:50:15] jean@megaweb.co.za what does your special url search feature do to your error logs? eg. www.php.net/findsomething I have been playing around with the idea of fetching content using 404 but even if I use header('HTTP/1.1 200 OK'); it still shows up in the server error logs. How do you get around this? ------------------------------------------------------------------------ [2002-08-14 21:54:22] rasmus@php.net The pages do actually change quite often given all the user notes. But yes, 600 may be too aggressive. ------------------------------------------------------------------------ [2002-08-14 05:32:44] sander@php.net I've fixed the 404's on /manual/*/print/*. ------------------------------------------------------------------------ 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/18897 -- Edit this bug report at http://bugs.php.net/?id=18897&edit=1