Hello!
On Mon, Nov 20, 2017 at 12:46:31PM -0500, shivramg94 wrote:
> I am trying to use nginx as a reverse proxy with upstream SSL. For this, I
> am using the below directive in the nginx configuration file
>
> proxy_pass https://;
>
> where "" is another file which has the list of
> upstream
Just one quick question. Does Nginx check if the upstream servers are
reachable via the specified protocol, during the reload process? If say, in
this case the upstreams are not accepting ssl connections, will the reload
fail?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,277399,27741
Hi,
try
1) curl -ivvv https:// to your upstreams.
2) add server :443 (if your upstreams accepting ssl connections on 443)
br,
Aziz.
> On 20 Nov 2017, at 20:46, shivramg94 wrote:
>
> I am trying to use nginx as a reverse proxy with upstream SSL. For this, I
> am using the below directi
I am trying to use nginx as a reverse proxy with upstream SSL. For this, I
am using the below directive in the nginx configuration file
proxy_pass https://;
where "" is another file which has the list of
upstream servers.
upstream {
server : weight=1;
keepalive 100;
}
With this configur
FWIW - I have found rate limiting very useful (with hardware LB as well as
nginx) but, because of the inherent burstiness of web traffic, I typically set
my threshold to 10x or 20x my expected “reasonable peak rate.”
The rationale is that this is a very crude tool, just one of many that need to
Thank you very much for clearing this out. All I need to do is
"limit_req_log_level warn;" and then I see limits as warn-logs and delaying
as info, and hence I only view warn+ levels, it is omitted from the logfile
completely.
---
Med venlig hilsen / Best Regards
Stephan Ryer Møller
Partner & CTO
I am trying to use nginx as a reverse proxy with upstream SSL. For this, I
am using the below directive in the nginx configuration file
proxy_pass https://;
where "" is another file which has the list of
upstream servers.
upstream {
server
: weight=1;
Hello!
On Mon, Nov 20, 2017 at 12:31:59PM +0100, DreamWerx wrote:
> I was hoping someone might have an idea here.. I have a number of nginx
> doing load balancing sitting behind AWS's network load balancers (TCP) -
> which seem to only support TCP checks.
>
> Recently a few have stopped working
Hello!
On Mon, Nov 20, 2017 at 11:33:26AM +0100, Stephan Ryer wrote:
> We are using nginx as a proxy server in front of our IIS servers.
>
> We have a client who needs to call us up to 200 times per second. Due to
> the roundtrip-time, 16 simultanious connections are opened from the client
> and
Hi all,
I was hoping someone might have an idea here.. I have a number of nginx
doing load balancing sitting behind AWS's network load balancers (TCP) -
which seem to only support TCP checks.
Recently a few have stopped working / frozen - they still seem to accept a
tcp connection from the NLB -
On Mon, Nov 20, 2017 at 02:59:39AM -0500, hook wrote:
> Hi
> I'm writing some module with using ngx_write_file. I found file's
> offset is incorrect, in this case:
> ```
> u_char av = 0x01 | 0x04;
> // file cur offset -> 4096;
> ngx_write_file(file, &av, 1, 4)
> ```
>
Hello
We are using nginx as a proxy server in front of our IIS servers.
We have a client who needs to call us up to 200 times per second. Due to
the roundtrip-time, 16 simultanious connections are opened from the client
and each connection is used independently to send a https request, wait for
x
Hi
I'm writing some module with using ngx_write_file. I found file's
offset is incorrect, in this case:
```
u_char av = 0x01 | 0x04;
// file cur offset -> 4096;
ngx_write_file(file, &av, 1, 4)
```
file->offset would be 4097, but real offset is 4096.
I'm confused
13 matches
Mail list logo
