Great.
proxy_http_version 1.1;
did the trick. Thank you.
PL
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,278217,278223#msg-278223
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Mon, Jan 22, 2018 at 6:02 AM Sékine Coulibaly
wrote:
> Hi,
>
> I'm evaluating Nginx Plus for a UDP Load Balancer but can't make it work.
> The packets are spoofed correctly on the LB side (as seen with tcpdump,
> where I can see packets created, the source IP being the one of the client,
> the
Hello!
On Mon, Jan 22, 2018 at 09:34:40AM -0500, plrunner wrote:
> I have an apache webserver in front of which I put my nginx 1.12.2 that is
> running with a basic proxy_pass configuration. I have done this a million
> times, even with more complex cofigurations.
>
> Everything works perfectly
Hi,
I have an apache webserver in front of which I put my nginx 1.12.2 that is
running with a basic proxy_pass configuration. I have done this a million
times, even with more complex cofigurations.
Everything works perfectly except one thing I recently noticed:
the login phase consists of a POST
Hi,
I'm evaluating Nginx Plus for a UDP Load Balancer but can't make it work.
The packets are spoofed correctly on the LB side (as seen with tcpdump,
where I can see packets created, the source IP being the one of the client,
the destination the one of the selected upstream). However, on the upstr
So some questions:
What hardware is this? Are they 16 “real” cores or hyper threaded cores?
Do you have a test case setup so you can readily measure the impact of change?
Many tunings that involve numa will only show substantial results ion specific
app
What does cat /proc/cpuinfo | tail -28 ret
