Hi,
I am using nginx as proxy with two upstream servers. In the access log, I
log the upstream_address, upstream_status, status (downstream), a special
response header from upstream, etc.
A few times I see in the log upstream_address: server1:port, server2:port
with upstream_status: 504, 502 st
Hello,
I noticed that the PGP key used for signing the Debian release packages
recently expired. I went to download the new one and noticed that nginx.org
wasn't using HTTPS by default. Manually entering a https URL works as
expected, although some pages have hard coded http links in them.
Is ther
On Friday 19 August 2016 09:25:46 t...@sina.com wrote:
> Hi,
>
> I have a scenario: my backend servers provide URL to query whether this sever
> can accept new connections (the http response body is "true" or "false").
> This server also has configuration for the max allowed session. Now I want
On Friday 19 August 2016 18:07:46 Sharan J wrote:
> Hi,
>
> Thanks for the response.
>
> Would like to know what happens in the following scenario,
>
> Client sets its initial congestion window size to be very small and
> requests for a large data. It updates the window size everytime when it
>
Ah that was stupid... i forgot to copy the php location from my other server
block
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,268988,269058#msg-269058
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi,
Thanks for the response.
Would like to know what happens in the following scenario,
Client sets its initial congestion window size to be very small and
requests for a large data. It updates the window size everytime when it
gets exhausted with a small increment (so send_timeout wont happen a
On Friday 19 August 2016 08:22:42 khav wrote:
[..]
> server {
> listen 80;
> server_name mywebsite.com;
> location = /upload {
> #module settings goes here
> upload_pass @uploadhandler;
> }
>
> location @uploadhandler {
> root /var/www/mywebsite.com/public_html/www;
> rewrite ^ /upload.ph
On Fri, Aug 19, 2016 at 02:12:28PM +0200, Alarig Le Lay wrote:
Hi there,
> bulbizarre ~ # cat /etc/resolv.conf
nginx doesn't use /etc/resolv.conf (directly, at any rate).
> I have some error messages about “no resolver defined”:
http://nginx.org/r/resolver
The answer is to tell nginx what res
Here is a simplified version of the config.I get 405 (Method not
allowed).Documentation for the module say that the error happen if the
request method is not POST
http://www.grid.net.ru/nginx/upload.en.html
server {
listen 443 http2;
location = /upload {
proxy_pass http://mywebsite.com/uplo
Hi,
On my server, I don’t have a v4 resolver, juste an IPv6 one:
bulbizarre ~ # cat /etc/resolv.conf
# Generated by dhcpcd from eth0.dhcp, eth0.ra
# /etc/resolv.conf.head can replace this line
domain swordarmor.fr
nameserver 2001:470:1f13:138::1
# /etc/resolv.conf.tail can replace this line
I hav
On Friday 19 August 2016 17:06:41 Sharan J wrote:
> Hi,
>
> Would like to know what timeouts should be configured to mitigate slow read
> attack in HTTP/2.
>
A quote from the commit:
| Now almost all the request timeouts work like in HTTP/1.x connections, so
| the "client_header_timeout", "cl
Hi,
Would like to know what timeouts should be configured to mitigate slow read
attack in HTTP/2.
Referred ->
https://trac.nginx.org/nginx/changeset/4ba91a4c66a3010e50b84fc73f05e84619396885/nginx?_ga=1.129092111.226709851.1453970886
Could not understand what you have done when all streams are st
Here is a simplified version of the config.I get 405 (Method not
allowed).Documentation for the module say that the error happen if the
request method is not POST
http://www.grid.net.ru/nginx/upload.en.html
server {
listen 443 http2;
location = /upload {
proxy_pass http://mywebsite.com/upl
13 matches
Mail list logo
