Hello!
On Sat, 2013-06-15 at 19:39 -0700, Paul N. Pace wrote:
> I have a server that I set up to run several domains from and it has
> worked great and without issue for about 6 months.
>
> I have another server that I had set up and was only running one
> domain from it and I just added a second
I'm sure it's something small you've
overlooked. Going to take a shot in the dark and say you've copy
and pasted your server blocks and perhaps forgot to change
something you needed to for that particular server.
Sajan Parikh
Owner, Noppix LLC
I have a server that I set up to run several domains from and it has
worked great and without issue for about 6 months.
I have another server that I had set up and was only running one
domain from it and I just added a second domain. For some reason, this
second server does not want to serve two d
Hello!
On Sat, Jun 15, 2013 at 02:58:33PM +0200, Matthijs Langenberg wrote:
> I am serving dynamic requests behind the Nginx HTTP server. HTTP requests
> are mostly from mobile HTTP clients. That's is why I care about two things.
>
> 1. Do not send the same representation twice: Use ETag caching
Hello!
On Fri, Jun 14, 2013 at 04:54:26PM +0200, Tu Tr wrote:
> Since proxy_pass by default uses HTTP 1.0 shouldn't it also clear the
> Connection header by default?
By default, nginx uses "Connection: close" in upstream requests
for maximum compatibility with various backend servers.
> This c
Hello!
On Fri, Jun 14, 2013 at 09:41:20AM -0300, Joseph Mingrone wrote:
> Is it possible to log the remote host name (as opposed to just the IP
> address) in the access log? I run a low traffic web server and I'm not
> concerned with the overhead for the lookups.
No.
--
Maxim Dounin
http://ng
Hello!
On Fri, Jun 14, 2013 at 12:05:10PM +0100, James Lee wrote:
> Hello,
>
> nginx 1.4.1 is truncating proxy output for large files.
[...]
> *** Other information ***
>
> This is similar to:
> http://mailman.nginx.org/pipermail/nginx/2012-April/033272.html
> The workaround for this was also
On Sun, Jun 16, 2013 at 01:01:37AM +0300, Vasil Kolev wrote:
> В 22:06 +0100 на 15.06.2013 (сб), Francis Daly написа:
> > But in this case, that's probably unnecessary, since you already know
> > that without the "if" statements, no problems appear.
> > Perhaps using a "map" to set values to be u
В 22:06 +0100 на 15.06.2013 (сб), Francis Daly написа:
> The usual first step would be to see whether the problem persists when
> you just use the distributed nginx, with no external modules or patches.
>
> But in this case, that's probably unnecessary, since you already know
> that without the "
On Sat, Jun 15, 2013 at 04:32:04PM +0300, Vasil Kolev wrote:
Hi there,
> Removing the ifs in the config fixes the problem, but that doesn't help
> me :)
>
> This is a compiled nginx from source, on debian stable (wheezy), with a
> few small additions available at
> https://github.com/krokodileri
Hello;
Is it possible to log the remote host name (as opposed to just the IP
address) in the access log? I run a low traffic web server and I'm not
concerned with the overhead for the lookups.
Thanks,
Joseph
___
nginx mailing list
nginx@nginx.org
htt
Hello,
I was trying to add rate limiting to our setup (mp4 file serving) and
got into some very strange issues.
First, with version 1.2.0, I was seeing the following:
2013/06/14 13:25:02 [emerg] 12470#0: *147816 malloc(18446744073709551608)
failed (12: Cannot allocate memory), client: 92.247.59
I am serving dynamic requests behind the Nginx HTTP server. HTTP requests
are mostly from mobile HTTP clients. That's is why I care about two things.
1. Do not send the same representation twice: Use ETag caching mechanism.
2. Make better us of available bandwidth: Use Accept-Encoding HTTP
compres
13 matches
Mail list logo
