Welcome! Log In Create A New Profile

Advanced

Re: slice module got error when contents of upstream was updated

Roman Arutyunyan
April 03, 2017 11:08AM
Hi,

On Mon, Apr 03, 2017 at 01:09:14AM -0400, t.nishiyori wrote:
> Helle,
>
> I'm using nginx with slice module as a proxy.
>
> One day, I got an error log such like a "etag mismatch in slice response
> while reading response header from upstream".
>
> The cause of this error was occurred when that some parts of response was
> cached before updating the upstream contents but others was not cached.
> So it's not be solved until the cache period is expired.
>
> Do you have any solutions for this error?
> I hope the slice module change the status of related caches to disable, when
> the slice module got this error.

It's supposed that the proxied response never changes. If it does, the module
aborts sending the response and produces the error you have mentioned.
There's no simple way of making the output consistent for changeable responses
without introducing a significant overhead.

--
Roman Arutyunyan
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

slice module got error when contents of upstream was updated

t.nishiyori April 03, 2017 01:09AM

Re: slice module got error when contents of upstream was updated

Roman Arutyunyan April 03, 2017 11:08AM

Re: slice module got error when contents of upstream was updated

t.nishiyori April 05, 2017 02:27AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 320
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