https://issues.apache.org/bugzilla/show_bug.cgi?id=55669
--- Comment #4 from Mike Rumph <[email protected]> --- Hello Graham, If you are referring to my setup, here is the response I get: - $ curl -v http://localhost:8080/ * About to connect() to localhost port 8080 * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8080 > GET / HTTP/1.1 > User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 > OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 > Host: localhost:8080 > Accept: */* > < HTTP/1.1 503 Service Unavailable < Date: Wed, 13 Nov 2013 20:17:30 GMT < Server: Apache/2.4.7-dev (Unix) < Content-Length: 299 < Cache-Control: max-age=600 < Expires: Wed, 13 Nov 2013 20:22:23 GMT < Age: 307 < Connection: close < Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>503 Service Unavailable</title> </head><body> <h1>Service Unavailable</h1> <p>The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</p> </body></html> * Closing connection #0 After the max-age expires, a normal response is returned. So I agree with you that this is in agreement with RFC 2616 section 13.4. - http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.4 But my setup is only an attempt to reproduce the bug report. Tod's results may be different. The only error I see at this point is in the wording of the documentation at the following location: - http://httpd.apache.org/docs/2.4/caching.html#http-caching - "What Can be Cached? - 2. The response must have a HTTP status code of 200, 203, 300, 301 or 410." This wording is not consistent with the last paragraph of RFC 2616 section 13.4. - "A response received with any other status code (e.g. status codes 302 and 307) MUST NOT be returned in a reply to a subsequent request unless there are cache-control directives or another header(s) that explicitly allow it." Thanks, Mike Rumph -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
