Hi,
Nginx reads from top to bottom, just like you. In your example, you are
returning 503 (an action) before instructing to use your custom error page.
Just need to put your instructions first, then your actions...like so:
error_page 500 502 503 504 /50x.html;
location = /50x.html { root /usr/sh
CM Fields Wrote:
---
When I get external authentication working with
> Nginx I would be happy to share the complete setup with the list.
>
> ___
> nginx mailing list
> nginx@nginx.org
> http://mailman.
Hello!
On Tue, Jul 30, 2013 at 7:49 PM, 卫越 wrote:
>>*) Change: now after receiving an incomplete response from a backend
>> server nginx tries to send an available part of the response to a
>> client, and then closes client connection.
>
> It is obviously different from previous n
>*) Change: now after receiving an incomplete response from a backend
> server nginx tries to send an available part of the response to a
> client, and then closes client connection.
It is obviously different from previous nginx, but I wonder why nginx made
this change.
__
We used amazon S3 as upstream server. And it does not serve 'Accept-Ranges:
bytes' as respond header. So the nginx proxy server will not serve range
response even if the content has been completely cached on the proxy
server.
We tested on a upstream server that do serve 'Accept-Ranges: bytes' as
re
Configuration:
==
- Nginx as reverse proxy + SSL negotiation
- Apache Tomcat.
- nginx version: nginx/1.5.2
built by gcc 4.1.2 20080704 (Red Hat 4.1.2-54)
TLS SNI support disabled
configure arguments: --with-rtsig_module --with-select_module
--with-poll_module --with-file-aio --with-http_s
On Thu, Jul 25, 2013 at 1:41 PM, Jonathan Matthews
wrote:
> I've just got to a box and can ACK that. I can make that stop with a
> correctly configured try_files, which I would always choose to have
> set up, myself. That may not be a solution for you however.
>
> Here's a way I've just tested (on
This can be ignored now, I've found the issue. It was samba locking the
file, adding "oplocks = no" to my smb.conf solved the problem.
Thanks
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241387,241389#msg-241389
___
nginx mailing list
ngin
To clarify above, when I say I change the EOL and encoding on both sublime
and notepad++ nothing changes. If notepad++ is windows EOL and ANSI it is
still fine loading first time, no matter what I set sublime too it's always
failing first load
Posted at Nginx Forum:
http://forum.nginx.org/read.ph
Hi Guys,
Got a strange issue happening, I do my coding on Windows 8 x64 using Sublime
Text 2.0.2, my sites run of a Ubuntu 13.04 VirtualBox guest over a bridged
adaptor connection.
Weird thing happens, if I save a static file (HTML, CSS etc) from Sublime on
Windows to my Ubuntu vm and load it I g
Hi.
If you compile nginx yourself, its not necessary to update system libraries
You can use openssl 1.0.1 source and use
--with-openssl=/var/tmp/openssl-1.0.1e
switch to configure options, where folder is the path where you unpacked the
source,
nginx will configure and compile openssl as static lib
Hello!
On Mon, Jul 29, 2013 at 2:44 PM, John Watson wrote:
> It seems the issue is v0.21 of http://wiki.nginx.org/NginxHttpSRCacheModule
> that causes this issue. I'll file a bug with agentzh on his Github repo.
>
Just for the reference, there is no bugs in ngx_srcache.
It's just that enabling m
This was quite tricky!
# apt-show-versions libssl-dev
libssl-dev/wheezy upgradeable from 0.9.8o-4squeeze14 to 1.0.1e-2
Thanks a lot for the help mate.
On Tue, Jul 30, 2013 at 6:15 PM, Valentin V. Bartenev wrote:
> On Tuesday 30 July 2013 17:51:21 kirpit wrote:
> > Hi,
> >
> > I simply read
On Tuesday 30 July 2013 17:51:21 kirpit wrote:
> Hi,
>
> I simply read every article on the net, followed the docs but simply can't
> get SPDY support working.
>
> It's running on Debian Squeeze (that I have to) so I upgraded OpenSSL to
> the version 1.0.1e from Wheezy repo. Downloaded the latest
Hi,
I simply read every article on the net, followed the docs but simply can't
get SPDY support working.
It's running on Debian Squeeze (that I have to) so I upgraded OpenSSL to
the version 1.0.1e from Wheezy repo. Downloaded the latest stable Nginx
1.4.2 then compiled with the configuration opti
Changes with nginx 1.5.3 30 Jul 2013
*) Change in internal API: now u->length defaults to -1 if working with
backends in unbuffered mode.
*) Change: now after receiving an incomplete response from a backend
server nginx tries to send a
I have the same problem.
Have you been able to find a solution to this? I believe it might need to be
fixed on the vpn side.
The setup works OK if the vpn server and nginx server are on different
machines, but if they are on the same machine, it doesn't work for me.
A more detailed description
17 matches
Mail list logo
