[PATCH] reset r->cache->valid_sec for following the redirect

2019-05-07 Thread Sangdeuk Kwon
# HG changeset patch # User Sangdeuk Kwon # Date 1557288704 -32400 # Wed May 08 13:11:44 2019 +0900 # Node ID c4e1be885640a8302dcbf97162b3cbdc21710a84 # Parent 16a1adadf43751f59257ba419f6bacd530dd19d3 reset r->cache->valid_sec for following the redirect this config:

[PATCH] reset r->cache->valid_sec for following the redirect

2019-05-15 Thread Sangdeuk Kwon
Thank you for your review > An obvious workaround is to ensure that such configuration do not > allow caching of responses, for example, by using "proxy_cache > off;" in such locations. If using "proxy_cache off;", all response is not cached. The expected behavior is 1. when 200 response, it

[PATCH] nginx cannot respond when big response header with proxy_buffering is off and limit_rate is set.

2019-10-14 Thread Sangdeuk Kwon
# HG changeset patch # User Sangdeuk Kwon # Date 1571119628 -32400 # Tue Oct 15 15:07:08 2019 +0900 # Node ID a484d65af8cefef5d6501872a6b72a0623fd9af4 # Parent 6208c5418c88ce8ecc656b40704a752cb7c7648a nginx cannot respond when big response header with proxy_buffering is off and limit_rate

[PATCH] When cache file is expired, nginx can make a lot of upstream requests.

2020-03-25 Thread Sangdeuk Kwon
# HG changeset patch # User Sangdeuk Kwon # Date 1585118845 -32400 # Wed Mar 25 15:47:25 2020 +0900 # Node ID fe5988cefe615bb0f2a8936221c8464a6664916e # Parent 0cb942c1c1aa98118076e72e0b89940e85e6291c When cache file is expired, nginx can make a lot of upstream requests. In cache miss case

[PATCH] When cache file is expired, nginx can make a lot of upstream requests.

2020-03-30 Thread Sangdeuk Kwon
Thank you for your explanation I have a question. Are there any directives for preventing multiple upstream and serving new content? expect case: 1st request: get new content from origin and serve new content. 2nd request: serve new content. 3rd request: serve new content. "proxy_cache_use stale

[PATCH] During background update, nginx can't add "Range" header

2020-07-22 Thread Sangdeuk Kwon
# HG changeset patch # User Sangdeuk Kwon # Date 1595481798 -32400 # Thu Jul 23 14:23:18 2020 +0900 # Node ID 90e5ccf7c229322079ba1b61b4241ed69dfc09b2 # Parent 4f30f75dbdf33d6fae9e70086e0df5cbab7db027 During background update, nginx can't add "Range" header If the c

[PATCH] During background update, nginx can't add "Range" header

2020-07-26 Thread Sangdeuk Kwon
> Hi, Thank you for your explanation. I added comments. Please check it one more time. >>* On 23 Jul 2020, at 08:29, Sangdeuk Kwon ><http://mailman.nginx.org/mailman/listinfo/nginx-devel>> wrote: *>> >>* # HG changeset patch >*>* # User Sangdeuk Kwon <

[PATCH] slice and gzip problem

2020-08-03 Thread Sangdeuk Kwon
# HG changeset patch # User Sangdeuk Kwon # Date 1596515879 -32400 # Tue Aug 04 13:37:59 2020 +0900 # Node ID 6ed0cfe89f288587b6815333bab798d6aedc6137 # Parent da8d758aabebbba833405463aa5a785b4c324495 slice and gzip problem When slice is enabled, client request content with "A

[PATCH] proxy_cache_max_range_offset could affect the background updating

2022-12-06 Thread Sangdeuk Kwon
# HG changeset patch # User Sangdeuk Kwon # Date 1670390583 -32400 # Wed Dec 07 14:23:03 2022 +0900 # Node ID a1069fbf10ffd806b7c8d6deb3f6546edc7b0427 # Parent 0b360747c74e3fa7e439e0684a8cf1da2d14d8f6 proxy_cache_max_range_offset could affect the background updating

Re: [PATCH] proxy_cache_max_range_offset could affect the background updating

2022-12-12 Thread Sangdeuk Kwon
# HG changeset patch # User Sangdeuk Kwon # Date 1670906112 -32400 # Tue Dec 13 13:35:12 2022 +0900 # Node ID 8c273203bd8e7280d3ce1895a37c7ef5323eea2b # Parent 56819a9491fe2ee1dcfe4986bed913b894fc0360 proxy_cache_max_range_offset could affect the background updating