> In my case, the number of hosts will change over time, and I can’t update
the nginx config. So I thought it would make sense to use a hostname that
resolves to many IPs. This would be a scalable solutioin
In that case, it makes sense to use a templating tool to dynamically
populate the content
Hi Maxim,
Thank you for your response.
OK, I understand what you have said.
This seems slightly strange to me. We both understand the purpose/point of
hashing (consistent or not consistent). Why does it then make sense to
fall-back to round robin?
In my case, the number of hosts will change
Hello!
On Sun, Feb 02, 2020 at 11:09:14PM -0800, Frank Liu wrote:
> When I send a request with too longer header value to nginx 1.16.1, I get
> 400 Bad Request response code and default nginx error page.
> If I create a custom error page:
> error_page 494 /my4xx.html;
> now I can see my error pag
Thanks for the reply!
My question is more about why there is inconsistent response code between using
default error page and default error page.
> On Feb 3, 2020, at 5:20 AM, Francis Daly wrote:
>
> On Sun, Feb 02, 2020 at 11:09:14PM -0800, Frank Liu wrote:
>
> Hi there,
>
>> When I send a r
Hello!
On Thu, Jan 30, 2020 at 10:55:03AM -0500, slowgary wrote:
> Thanks for the correction Maxim. I tested this before posting by using an
> old certificate. Nginx did not throw an error but the browser did notify
> that the connection was insecure.
Depending on what exactly "certificate chain
On Sun, Feb 02, 2020 at 11:09:14PM -0800, Frank Liu wrote:
Hi there,
> When I send a request with too longer header value to nginx 1.16.1, I get
> 400 Bad Request response code and default nginx error page.
> If I create a custom error page:
> error_page 494 /my4xx.html;
> now I can see my error
Hello!
On Sat, Feb 01, 2020 at 11:48:00AM -0800, Ian Morris Nieves wrote:
> Here is the setup:
> - I am running nginx in a single docker container and it has an
> upstream to a docker service which is composed of 3 docker
> containers (which happens to be php-fpm)
> - the service is configured
Hi guys,
since I cannot login into trac (no OAuth handler found), I'll try reporting
it here. We are experiencing segmentation faults on nginx 1.16.1 with
post_action.
CentOS:
# cat /etc/centos-release
CentOS Linux release 7.6.1810 (Core)
Nginx:
# nginx -V
nginx version: nginx/1.16.1
built by gcc