GitHub user pandareen opened a pull request:
https://github.com/apache/tomcat/pull/115
Setting Timezone to GMT for Expires Header as per RFC1123
Tomcat response header 'Expires' is getting formatted into timezone based
string and not just 'GMT' as spec
Github user pandareen commented on the issue:
https://github.com/apache/tomcat/pull/115
@michael-o I think 0 would be confusing. Preformatted string in static
final sounds simpler to me.
---
-
To unsubscribe, e
Github user pandareen commented on the issue:
https://github.com/apache/tomcat/pull/115
@michael-o I built tomcat using `Expires` header as `0`, but chrome is
still not understanding.
Here's a screenshot: [https://i.imgur.com/cSnuVIr.png
Github user pandareen commented on the issue:
https://github.com/apache/tomcat/pull/115
Okay let me explain.
Case 1. [https://i.imgur.com/tofjYaM.png](https://i.imgur.com/tofjYaM.png)
- When chrome gets a `Cache-Control: no-cache` directive in response header, it
sends `If
Github user pandareen commented on the issue:
https://github.com/apache/tomcat/pull/115
Good thought @michael-o. I'll get some info from chromium...
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apach
