Hello,
we have observed a case where it seems that the proxy_cache_valid directive is
ignored.
nginx version: 1.19.9
Config: proxy_cache_valid 200 206 30d;
Scenario:
* A cache file was corrupted (a file system issue). A part of the section that
contains the headers had been overwritten with
See below for more questions (I snipped repetitive stuff that was not
necessary for understanding):
Francis Daly Wrote:
---
> On Sun, Feb 06, 2022 at 10:08:49PM -0500, marioja2 wrote:
>
(snip)
> The request that you care about is a POST to a url
Hi, I ran another case with error_log debug. Here are 4 files:
error.log.2: https://1drv.ms/u/s!ApcymW6zCVpnuxyYecXcaIlqrVWu?e=WmgaVO
error.log.1: https://1drv.ms/u/s!ApcymW6zCVpnuxt2oIE3eLklkND0?e=ZlJNGH
access.log.2: https://1drv.ms/u/s!ApcymW6zCVpnuxgl1jCmHH8O-Pmi?e=GJGQgI
access.log.1: https:
I have a IPv4 to IPv6 reverse proxy server so that IPv4 clients can access
IPv6 only websites. For each website the website domain and the
corresponding IPv6 address must be added manually. Is there a way to
automatically detect the record from the website and use this in
upstream?
stream {
On Sun, Feb 06, 2022 at 10:08:49PM -0500, marioja2 wrote:
Hi there,
> I checked and the output when starting from docker-compose up -d or
> docker-compose restart is identical. I include it here:
> https://1drv.ms/u/s!ApcymW6zCVpnuwKQOFFbSCLiZhn9?e=bvrpJU
Thanks; that is useful to see what nginx
