httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 9673] - Conditional GET requests not handled properly with filtered content
Date Thu, 06 Jun 2002 21:25:15 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9673>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9673

Conditional GET requests not handled properly with filtered content





------- Additional Comments From ck-bugzilla@newsclub.de  2002-06-06 21:25 -------
As I understand, the problem is the filter concept itself.    
Filters are applied on data that is already processed by http_protocol.c    
    
What http_protocol.c checks is the modification time of a file, ie.    
"index.php". The script has been written in 2001, for example, but it produces    
new content from a database every minute.    
    
So, the PHP code gets only executed, if Apache decides to pass the data to the    
filter. Here Apache decides not to, because it thinks that the file has not    
changed.    
    
The ETag is probably generated because Apache looks at the program code of    
index.php itself, not at the content the PHP script produces.    
   
I suggest to add an Apache directive to disable If-Modified-Since processing   
for Filtered files, for example:   
   
<FilesMatch "\.php$">   
    SetInputFilter PHP   
    SetOutputFilter PHP   
    CheckIfModifiedSince off   
</FilesMatch>   
   
PHP itself could then automatically set this directive.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message