Changes between Initial Version and Version 1 of Ticket #2176
- Timestamp:
- 05/03/21 13:22:50 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2176 – Description
initial v1 5 5 I thought that reading source code should be the best solution to understand how etags are generated and how Nginx uses them to generate 304 responses. But I was surprised to read that in {{{src/http/modules/ngx_http_not_modified_filter_module.c}}}: 6 6 7 {{{ 7 {{{#!c 8 8 if (r->headers_in.if_modified_since 9 9 && ngx_http_test_if_modified(r)) … … 24 24 25 25 So, to be sure that resource validation via etags was done after last modified times, I deactivate {{{If-Modified-Since}}} check with directive {{{if_modified_since off;}}}. After that, I no longer got any 304 responses but only 200 ones. I thought that etag check didn't work, but reading {{{ngx_http_test_if_modified}}} function gave me a clue: 26 {{{ 26 {{{#!c 27 27 static ngx_uint_t 28 28 ngx_http_test_if_modified(ngx_http_request_t *r)