Thank you Francis, your answer is exhaustive, as always.
--- Original message ---
From: "Francis Daly"
Date: 20 June 2013, 00:27:48
> On Wed, Jun 19, 2013 at 09:22:11PM +0300, wishmaster wrote:
>
> Hi there,
>
> > From http://wiki.nginx.org/Pitfalls I use two server's {} directives for
On Wed, Jun 19, 2013 at 06:44:55PM +0200, mailinglis...@simonhoenscheid.de
wrote:
Hi there,
> This is still driving me mad. We need the expire header for images, but
> if we add the location above, our rules arent processed anymore. If we
> add the expire-header to the locations with the rewri
On Wed, Jun 19, 2013 at 09:22:11PM +0300, wishmaster wrote:
Hi there,
> From http://wiki.nginx.org/Pitfalls I use two server's {} directives for this
> instead if().
> But this doesn't work and first server {} directive MUST have listen
> directive as well.
http://nginx.org/en/docs/http/reque
I do a custom-build for our own servers (in private pkg-ng repository)
with a handful of useful modules included. Because the truth is: only
you know what modules you want or need.
This is absolutely true. (And I'm running CentOS and have been very
happy as well.)
Thanks.
_
Am 19.06.2013 um 21:04 schrieb AJ Weber :
> Is anyone maintaining a "current" version of nginx with mod-security
> linked-in?
>
> I realize this is a bit lazy on my part -- the instructions seem relatively
> straightforward to build -- but I didn't want to "re-invent the wheel" if I
> didn't
Is anyone maintaining a "current" version of nginx with mod-security
linked-in?
I realize this is a bit lazy on my part -- the instructions seem
relatively straightforward to build -- but I didn't want to "re-invent
the wheel" if I didn't have to.
Thanks,
AJ
Hi, guys!
E.g. I have server new_server_name.com and want to rewrite requests to
www.new_server_name.com and old_server_name.com to present server.
>From http://wiki.nginx.org/Pitfalls I use two server's {} directives for this
>instead if().
server {
server_name www.new_server_name.com old_se
TL;DR:
Any nginx setting to say 'if a vhost's ssl settings are broken, skip it and
don't fail to start' ?
I've certainly RTFM'd this and peered at the source, but I figured I might
as well throw it out there, in case there's some hidden setting I've missed.
I'm building a reverse proxy config for
Many thanks Maxim, sometimes the solution is so easy. I was using SPDY and
only checked with latest Firefox and Chrome. And one shouldn't trust Page
Speed, it keeps telling me about the vary headers, although it's using SPDY.
Again, many thanks.
Posted at Nginx Forum:
http://forum.nginx.org/read.
Am 14.06.2013 14:11, schrieb mailinglis...@simonhoenscheid.de:
I have found the point where my rules break,
I've had the following location on top, to enable browser caching for
images, for one month:
#images give caching response for 1 month, browser will request after
this period of time agai
Hello!
On Wed, Jun 19, 2013 at 08:52:14AM -0400, Fleshgrinder wrote:
> I'm running the latest development version of nginx and gzipping is working.
> But no Vary Accept-Encoding header is added to any gzip response. The
> gzip_http_version isn't affecting the behavior, no matter if I set it to 1.
On 19 June 2013 14:19, solitaryr wrote:
> Thanks, Lucas. We looked at the headers being passed back (that's what the
> jsp was for). Even with http completely disabled and https only available,
> they were still passed as http:80 by nGinx...but Apache passed them through.
I don't understand wha
Thanks, Lucas. We looked at the headers being passed back (that's what the
jsp was for). Even with http completely disabled and https only available,
they were still passed as http:80 by nGinx...but Apache passed them through.
We tried this on two separate environments.
I looked at the ajp m
I'm running the latest development version of nginx and gzipping is working.
But no Vary Accept-Encoding header is added to any gzip response. The
gzip_http_version isn't affecting the behavior, no matter if I set it to 1.0
or 1.1 no header is sent. Even if I add the header myself via the add_heade
On Wed, Jun 19, 2013 at 05:28:51AM -0400, angelochen960 wrote:
Hi there,
> there is another one, but more specific, but it comes before location ~
> ^/images/:
>
> location ~ "^(/images/)(\d{1})/(\d{2})/(.*\.jpg$)" {
> }
If the only two "location" blocks in your server are:
location ~ "^(/im
You are right, thanks to Francis too for giving me the right direction to
look for the problem, it's really the other location that should have the
expires set as well, thanks.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,240201,240208#msg-240208
_
Hello!
On Wed, Jun 19, 2013 at 05:28:51AM -0400, angelochen960 wrote:
> there is another one, but more specific, but it comes before location ~
> ^/images/:
>
> location ~ "^(/images/)(\d{1})/(\d{2})/(.*\.jpg$)" {
> }
There is no such thing as "more specific" when you are talking
about regular
there is one before that:
location ~ "^(/images/)(\d{1})/(\d{2})/(.*\.jpg$)" {
}
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,240201,240206#msg-240206
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
there is another one, but more specific, but it comes before location ~
^/images/:
location ~ "^(/images/)(\d{1})/(\d{2})/(.*\.jpg$)" {
}
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,240201,240205#msg-240205
___
nginx mailing list
nginx@ng
On Wed, Jun 19, 2013 at 12:03:35AM -0400, angelochen960 wrote:
Hi there,
> location ~ ^/images/ {
> root /var/www
> expires max;
> }
>
> if I do a curl -I http://localhost/images/sample.jpg, I got following
> headers, but can not find the "Expires" in the headers, what I did wron
20 matches
Mail list logo
