On Sun, Oct 30, 2022 at 11:56:39AM -0600, Brian Carey wrote:
Hi there,
> Thinking it through though I think my solution is bad since it implies a
> dependency between the urls defined in the program and the location used in
> nginx, ie. they must match and the program cannot be proxied at an
On Tue, Nov 01, 2022 at 10:07:37PM +, Francis Daly wrote:
> On Wed, Nov 02, 2022 at 12:29:49AM +0800, Drweb Mike wrote:
Hi there,
> > My front end is nginx using reverse proxy work with my backend, I was
> > trying to cache images files only, but it seems doesn't work at all, the
> >
On Wed, Nov 02, 2022 at 12:29:49AM +0800, Drweb Mike wrote:
Hi there,
> My front end is nginx using reverse proxy work with my backend, I was
> trying to cache images files only, but it seems doesn't work at all, the
> *$no_cache* always output default value "proxy", which should be "0" when I
>
hi there
My front end is nginx using reverse proxy work with my backend, I was
trying to cache images files only, but it seems doesn't work at all, the
*$no_cache* always output default value "proxy", which should be "0" when I
visit image files
here it is my config
map
Hello!
On Tue, Nov 01, 2022 at 08:15:48PM +0900, Won-Kyu Park wrote:
> # HG changeset patch
> # User Won-Kyu Park
> # Date 1667298839 -32400
> # Tue Nov 01 19:33:59 2022 +0900
> # Node ID c964b33d60679f5cd8d43a8f859d16c2ac6f89e1
> # Parent 1ae25660c0c76edef14121ca64362f28b9d57a70
> fix
Ok fixed the patch and yup working now! No more socket() 0.0.0.0:80 failed
(94: Socket type not supported) errors when listen directive is not
specifically set.
Thanks Roman!
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,295642,295646#msg-295646
That was a quick reply, was about to pop on Nginx slack channel :)
Tried the patch but getting
patching file src/http/ngx_http_core_module.c
patch: malformed patch at line 18: lsopt.socklen = sizeof(struct
sockaddr_in);
Posted at Nginx Forum:
Hello!
On Mon, Oct 31, 2022 at 04:07:00PM +0400, Roman Arutyunyan wrote:
> While testing the feature, it became clear that 107 bytes as maximum PROXY
> protocol header size may not be enough. This limit came from v1 and stayed
> unchanged when v2 was added. With this limit, there are only 79
Hi George,
On Tue, Nov 01, 2022 at 08:19:15AM -0400, George wrote:
> I tested nginx-quic https://quic.nginx.org/README for HTTP/3 over QUIC using
> quictls openssl 1.1.1q forked library and ran into an interesting error for
> non-HTTPS nginx vhost configurations. If non-HTTPS nginx vhost doesn't
I tested nginx-quic https://quic.nginx.org/README for HTTP/3 over QUIC using
quictls openssl 1.1.1q forked library and ran into an interesting error for
non-HTTPS nginx vhost configurations. If non-HTTPS nginx vhost doesn't
specifically list the listen directive for port 80, I get this error when
# HG changeset patch
# User Won-Kyu Park
# Date 1667298839 -32400
# Tue Nov 01 19:33:59 2022 +0900
# Node ID c964b33d60679f5cd8d43a8f859d16c2ac6f89e1
# Parent 1ae25660c0c76edef14121ca64362f28b9d57a70
fix ngx_realpath() for win32
diff -r 1ae25660c0c7 -r c964b33d6067 src/os/win32/ngx_files.c
The 400 (Bad Request) status code indicates that the server cannot or will
not process the request because the received syntax is invalid, nonsensical,
or exceeds some limitation on what the server is willing to process. It
means that the request itself has somehow incorrect or corrupted and the
12 matches
Mail list logo
