diff options
| author | Luca Toscano <elukey@apache.org> | 2016-08-26 13:00:44 +0200 |
|---|---|---|
| committer | Luca Toscano <elukey@apache.org> | 2016-08-26 13:00:44 +0200 |
| commit | df532849b09111aa77a1d427a562eb2644fc8ab1 (patch) | |
| tree | 85354d7409afceef877e1367445b743b35f55dee /server/gen_test_char.c | |
| parent | Sync (diff) | |
| download | apache2-df532849b09111aa77a1d427a562eb2644fc8ab1.tar.xz apache2-df532849b09111aa77a1d427a562eb2644fc8ab1.zip | |
After a long discussion in dev@ I reviewed my previous commit to only warn
the admins about Last-Modified header violations rather than trying
to interpret datestrings (like the ones not in GMT).
I also added explicit comments to summarize the current assumptions,
so it will be easier for somebody in the future to modify the code.
The following use cases are covered:
1) (F)CGI backend sends a Last-Modified header not in GMT and considered in the future by httpd (like now() in the EU/Paris timezone)
2) (F)CGI backend sends a Last-Modified header not in GMT and not considered in the future by httpd (like now() + 2 hours in the PST timezone)
3) (F)CGI backend sends a Last-Modified header in GMT but with a datetime in the future
Suggestions and opinion are really welcome.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1757818 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'server/gen_test_char.c')
0 files changed, 0 insertions, 0 deletions