Re: "If-Modified-Since" headers

JR>> Sorry I'm not sure what you mean here... It would only have to watch for JR>> *one* header -- Last-Modified. The web browser sends If-Modified-Since as JR>> part of the HTTP request, so it will be available and ready before script JR>> parsing begins. No, you need to seek it out in web-server headers. Nothing is "available and ready". On Apache this part is probably pretty easy, but it has to be done anew for every SAPI module. Also, I don't understand why at all PHP should go down to such a low-level things. After all, it's webserver work. Each content handler should not reinvent all HTTP mechanics. Apache has a function for that, ap_scan_script_header_err_buff. But I don't know where it fits in the SAPI. Anyone? JR>> Well, I sincerely hope it is implemented. :) As I said before, JR>> this "lack of functionality" hurts PHP's own web site too. JR>> Whoever wrote JR>> http://www.php.net/include/shared-manual.inc went JR>> to great lengths to calculate a Last-Modified date, when in JR>> reality it is useless since PHP ignores If-Modified-Since. (I'm Well, not exactly true. Last-Modified is used by caches even without If's. -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ +972-3-6139665 ext.106