On Sunday 07 August 2016 08:43:04 anish10dec wrote:
> Hi Everyone,
>
> We are using Nginx as Caching Server .
>
> As per Nginx Documentation by default nginx caches 200, 301 & 302 response
> code but we are observing that if Upstream server gives error 400 or 500 or
> 503, etc , response is get
On Sun, Aug 7, 2016 at 9:27 AM, Maxim Dounin wrote:
> Hello!
>
> On Sat, Aug 06, 2016 at 01:36:41PM -0400, sven falempin wrote:
>
>> I am trying to send files to nginx dav mod with perl.
>> When using simple transfer with one big chunk in the BODY
>> it s ok.
>>
>> But if i want to send the file c
Hello!
On Sat, Aug 06, 2016 at 01:36:41PM -0400, sven falempin wrote:
> I am trying to send files to nginx dav mod with perl.
> When using simple transfer with one big chunk in the BODY
> it s ok.
>
> But if i want to send the file chunk by chunk, i have issue.
>
> I am trying to figure out if
Check if your backend server is setting cache headers on errors like
Cache-Control / Expires.
Nginx by default uses these headers to know if the response should be
cached or not.
When these headers are not present it uses the configuration done with
proxy_cache_valid.
On Sun, Aug 7, 2016 at 9:43
Hi Everyone,
We are using Nginx as Caching Server .
As per Nginx Documentation by default nginx caches 200, 301 & 302 response
code but we are observing that if Upstream server gives error 400 or 500 or
503, etc , response is getting cached and all other requests for same file
becomes HIT.
Th
