RSS

2018-07-07 Thread Gena Makhomed
Hello, All! RSS https://hg.nginx.org/nginx/atom-log https://hg.nginx.org/pkg-oss/atom-log https://hg.nginx.org/nginx.org/atom-log stop working, instead of RSS feed html+javascript returned. RSSOwl can't execute javascript and don't see these RSS feeds. Also I can't download

SSL errors, verbosity level

2018-07-07 Thread shiz
Hi, I see those messages in my error logs daily. ``` 2018/07/07 08:01:32 [crit] 31935#31935: *342781 SSL_do_handshake() failed (SSL: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol) while SSL handshaking, client: 173.208.91.177, server: 0.0.0.0:443 2018/07/07

Re: proxy_cache_background_update leads to 200 ms delay

2018-07-07 Thread Lucas Rolff
It's not a combination of tcp_nopush and proxy_cache_background_update that creates this delay. tcp_nopush (TCP_CORK in Linux) introduces a delay of packets being sent for up to 200ms or until the packet size gets to the defined MTU. proxy_cache_background_update (if I remember correctly),

Re: proxy_cache_background_update leads to 200 ms delay

2018-07-07 Thread stephan13360
Wow, thats it! The delay is gone. For now I am satisfied that the delay is gone and will read up some more on tcp_nopush. For the future: Is there any information on why the combination of tcp_nopush and proxy_cache_background_update create the delay and not the STALE response you get when the

Re: proxy_cache_background_update leads to 200 ms delay

2018-07-07 Thread Valentin V. Bartenev
On Friday, 6 July 2018 15:32:07 MSK stephan13360 wrote: > I recently set proxy_cache_valid 200 to 1 second, down from 15 minutes to > refresh the content more often (With proxy_cache_background_update on; > already activated long before that). > Our Web monitoring, checking our site every minute,