June 11, 2021 08:14AM
Hi Team,

Though we have proxy cache valid defined to cache only respective response code , nginx caching 416 response.

proxy_cache_valid 200 206 10d;
proxy_cache_key $uri$http_range;

416 is returned from upstream server and its getting cached on Ngnix.

Even with default settings by not specifying http response behavior is same.
proxy_cache_valid 10d;

Sample response cached on CDN for 416 Response

KEY: /content/entry/wvdata/68/49/314af040c2c611ebad1619ca96fe25b8_2492_a.mp4bytes=12130626-12373254
HTTP/1.1 416 Requested Range Not Satisfiable^M
Server: nginx^M
Date: Tue, 01 Jun 2021 15:10:06 GMT^M
Content-Type: text/html^M
Content-Length: 190^M
Connection: close^M
Expires: Thu, 01 Jul 2021 14:10:43 GMT^M
Cache-Control: max-age=2592000^M
Access-Control-Allow-Origin: *^M
Access-Control-Allow-Methods: GET, POST, OPTIONS^M
Access-Control-Allow-Headers: DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type^M
Content-Range: bytes */4194304^M
Subject Author Posted

416 HTTP Response Issue

anish10dec June 11, 2021 08:14AM

Re: 416 HTTP Response Issue

Francis Daly June 11, 2021 08:30AM

Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 260
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready