Hello,

We have a "chain" of nginx servers, like this:
A (nginx) -> B (nginx) -> C (anything)

B being A’s upstream, and C being B’s upstream

We ran into an issue where the files were being cached for a too long
duration. For example if we want to cache our files in this chain for
10 seconds, it could happen that the file actually exist for up to 30
seconds, because when B retrieves the file from C, even if it’s almost
expired on C, B will cache it for 10 seconds. Same thing if A retrieves
the file cached by B.

To fix this issue, nginx needs to properly take into account the Age
header provided by its upstream. This is what the attached patch does.

A subsequent patch will by provided soon, where the Age provided by
nginx actually indicates the age of the file in nginx’s cache, instead
of the age that was provided by its upstream.

Regards,

--
Florent Le Coz
Smartjog

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel