Hello!
On Mon, Feb 27, 2017 at 05:53:30AM -0500, jeanpaul wrote:
> I verified the patch and it seems to work!
> Thanks for your prompt solution on this.
Committed, thanks for testing.
http://hg.nginx.org/nginx/rev/8b7fd958c59f
--
Maxim Dounin
http://nginx.org/
_
Hi Maxim,
I verified the patch and it seems to work!
Thanks for your prompt solution on this.
JP
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,272622,272638#msg-272638
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailma
Hello!
On Sun, Feb 26, 2017 at 01:08:02PM -0500, jeanpaul wrote:
> I stripped down my configuration and removed 'unneeded' parts to reproduce.
>
> I'm able to reproduce it with the following settings:
>
> location / {
> # Added to mitigate the issue. Removed for testing
> #rewrite
Hi Maxim,
I stripped down my configuration and removed 'unneeded' parts to reproduce.
I'm able to reproduce it with the following settings:
location / {
# Added to mitigate the issue. Removed for testing
#rewrite ^/index.html$ / break;
proxy_pass http://backends;
proxy_
Hello!
On Sun, Feb 26, 2017 at 10:43:53AM +0100, Jean-Paul Hemelaar wrote:
> Hi all,
>
> I tested the new proxy_cache_background_update function to serve stale
> content while fetching an update in the background.
>
> I ran into the following issue:
> - PHP application running on www.example.co
Hi all,
I tested the new proxy_cache_background_update function to serve stale
content while fetching an update in the background.
I ran into the following issue:
- PHP application running on www.example.com
- Root document lives on /index.php
As soon as the cache has expired:
- A client request
