You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2012/10/08 17:12:03 UTC

[Bug 53539] content type and character set are changing when the content served from disk_cache becomes 'stale'

https://issues.apache.org/bugzilla/show_bug.cgi?id=53539

--- Comment #12 from Paul Beckett <p....@uea.ac.uk> ---
I think this patch has made it into Apache 2.4.3, and have been using that to
retest the same scenario (serving stale content from disk cache, due to
Proxyied location being unavailable) I previously described.

This now works perfectly for me in Google Chrome, but I am extremely puzzled as
to why Internet Explorer and Firefox are returning 503 Service Unavailable
responses.

The HTTP header in chrome shows:
HTTP request status: 200 (OK)
Name    Value
Date    Mon, 08 Oct 2012 13:05:17 GMT
Content-Encoding    gzip
Connection    close
Content-Length    6359
Server    Apache-Coyote/1.1
Vary    Accept-Encoding
Strict-Transport-Security    max-age=31536000; includeSubDomains,
max-age=31536000; includeSubDomains
Content-Type    text/html; charset=iso-8859-1
Warning    111 Revalidation failed
Expires    Mon, 08 Oct 2012 14:15:18 GMT

The expires time is in the past (point where it became stale I think).

I have tried accessing it from another PC to make absolutely sure I'm not
seeing any effect from client PC caching stuff, and get the same difference in
browser / apache behaviour.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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