Hi Nginx guru,
I am a new nginx user working on implementing a protected upload and
download service based on nginx. With an older version 1.4.6 I was able to
make it work. But since we upgraded it to 1.10.1 it seems the POST method
is changed to GET during the redirect. I saw Maxim had a post (
Hi,
I use an nginix server with multiple servers each with a matching upstream.
They are all in individual files in sites-enabled (ubuntu server).
Here is an example of such a config file:
upstream x.com {
server x.com:12908;
keepalive 65;
}
server {
listen 12908;
On 05/12/2016 17:12, Maxim Dounin wrote:
Hello!
On Mon, Dec 05, 2016 at 02:40:27PM +, Steven Hartland wrote:
snip...
Given that the real local address of the listening socket as shown
by netstat is 10.10.96.146, it means that the socket was created
when there were no explicit 127.0.0.1 in
Hello!
On Mon, Dec 05, 2016 at 02:40:27PM +, Steven Hartland wrote:
> On 05/12/2016 13:27, Maxim Dounin wrote:
> > Hello!
> >
> > On Sun, Dec 04, 2016 at 09:39:59PM +, Steven Hartland wrote:
[...]
> >> I believe the change to add a localhost bind to the server in question
> >> was relat
On 05/12/2016 13:27, Maxim Dounin wrote:
Hello!
On Sun, Dec 04, 2016 at 09:39:59PM +, Steven Hartland wrote:
We've used nginx for years and never had an issue with nginx upgrade
until today where the upgrade command ran but almost instantly after the
new process exited.
/usr/local/etc/rc.
Hello!
On Sun, Dec 04, 2016 at 09:39:59PM +, Steven Hartland wrote:
> We've used nginx for years and never had an issue with nginx upgrade
> until today where the upgrade command ran but almost instantly after the
> new process exited.
>
> /usr/local/etc/rc.d/nginx upgrade
> Performing san
