I am facing issue wherein nginx throws 412 for If-Match even when response header etag value matches it for a GET request. Also request is being handled via X-Accel-Redirect flow having few hops Here's sample debug error log for clue 2017/01/31 20:55:28 795#0: *6 http upstream process header 2017/01/31 20:55:28 795#0: *6 malloc: 0000000002389820:32768 2017/01/31 20:55:28 795#0: *by yogeshorai - Nginx Mailing List - English
I am facing similar issue wherein nginx throws 412 for If-Match even when response header etag value matches it for a GET request. Also request is being handled via X-Accel-Redirect flow having few hops Here's sample debug error log for clue 2017/01/31 20:55:28 795#0: *6 http upstream process header 2017/01/31 20:55:28 795#0: *6 malloc: 0000000002389820:32768 2017/01/31 20:55:28 795#0:by yogeshorai - How to...
Hi, We are using proxy_cache_lock feature of nginx and have set proxy_cache_lock_age and proxy_cache_lock_timeout attributes. To monitor and get overall stats we are looking for nginx log generated and any option to add some proxy cache lock based numbers to log entries. Some info about request being on hold or time wait under proxy lock criteria and time spent for the same. Any input wiby yogeshorai - Nginx Mailing List - English
Thnx maxim for pointing it out. We investigated further and issue seems to be at our back-end server. Thanks a lot for your helpby yogeshorai - Nginx Mailing List - English
We are facing this weird behavior wherein if a range request with Accept-Encoding:“gzip,deflate" is called for a url having .pdf as part of path, nginx would throw 416 even if the range is well within overall size of source file Also this happens for Range request "Range: bytes=20-" and above while same would work if its less that 20 bytes as start of range eg "Range: byby yogeshorai - Nginx Mailing List - English
I came across this strange behavior when we wanted to get Etag propagated through X-redirect chain as part of Http response for Range request ie Http 206.It seems nginx filters out any additional costume headers / tmp variable as part of final response through x-redirect for non-200 response. Kindly suggest workaround this issue. Here's a Log data under debug mode for Normal vs Range request cby yogeshorai - Other discussion