On Fri, Jun 11, 2021 at 07:29:10PM -0400, hgv wrote:
> Out of curiosity, I launched a fresh Ubuntu 20.04 AWS instance. Its file
> system structure matches the one you have. My installation is upgraded
> originally from 16.04 to 18.04 to 20.04. Therefore, I also checked a fresh
> Ubuntu 16.04. Its f
Out of curiosity, I launched a fresh Ubuntu 20.04 AWS instance. Its file
system structure matches the one you have. My installation is upgraded
originally from 16.04 to 18.04 to 20.04. Therefore, I also checked a fresh
Ubuntu 16.04. Its file system structure matches mine.
Hence, it looks like the
On Fri, Jun 11, 2021 at 08:14:22AM -0400, anish10dec wrote:
Hi there,
> Though we have proxy cache valid defined to cache only respective response
> code , nginx caching 416 response.
http://nginx.org/r/proxy_cache_valid
"""
Parameters of caching can also be set directly in the response
header.
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 spe
