[mod-security-users] Web brower cache enabling response headers missing
Brought to you by:
victorhora,
zimmerletw
From: <Rob...@ao...> - 2007-11-07 05:30:08
|
Hello all, I am trying to help my hosting service provider solve what seems to be a problem with mod_security implementation. For static HTML pages (page.htm, page.html) over an HTTP connection (not HTTPS) the server is currently sending only the following response headers to the web browser: HTTP/1.1 200 OK Date: Sun, 04 Nov 2007 18:42:36 GMT Server: WebServerX X-Powered-By: PHP/4.4.7 Connection: close Transfer-Encoding: chunked Content-Type: text/html That's a problem for me because there is nothing in the headers that would enable a web browser to "decide" whether or not to cache the web page - minimally: content-length and last-modified headers. Image mime types are being served with that information plus an Etag. I have a lot of related questions but I'll limit myself to one (three part) for now: Is it likely that the configuration of the server including use of mod_security is bollixed, thus resulting in the unusually sparse headers -or- is this likely something that was done deliberately to protect the server and its users -or- is this an unfortunate and unavoidable side effect of response body filtering using mod_security? Thank you, Rob ************************************** See what's new at http://www.aol.com |