On Wed, Dec 11, 2013 at 10:10:44AM -0800, r...@sent.com wrote:
oops. not quite ...
on systems where ld.so.conf does NOT point to the pcre path -- i.e, on
my production rather than dev boxes -- the RUNTIME link is incorrect,
ldd objs/nginx | egrep -i pcre
libpcre.so.1 =
details: http://hg.nginx.org/nginx/rev/e7b3b9855be8
branches:
changeset: 5466:e7b3b9855be8
user: Valentin Bartenev vb...@nginx.com
date: Wed Dec 11 21:30:38 2013 +0400
description:
Use ngx_chain_get_free_buf() in pipe input filters.
No functional changes.
diffstat:
Setting LD_LIBRARY_PATH in environment might work,
please consult with your runtime linker documentation.
Some runtime linkers allow you to override paths
enforced by -rpath, see LD_LIBRARY_PATH_RPATH in
http://man.freebsd.org/rtld for one such example.
But this has nothing to do with nginx.
details: http://hg.nginx.org/nginx/rev/f6258a7092e4
branches:
changeset: 5467:f6258a7092e4
user: Maxim Dounin mdou...@mdounin.ru
date: Thu Dec 12 20:28:48 2013 +0400
description:
Trailing whitespace fix.
diffstat:
src/http/modules/ngx_http_uwsgi_module.c | 2 +-
1 files changed,
In the ngx_pagespeed module we produce css files which refer to either
foo.webp or foo.jpg depending on whether the user agent we're serving
them to advertises webp support in the Accept header. We would like
to serve these publicly cacheable with Vary: Accept. Because css is
text-based these
Hello,
Weak ETAGs proved to be insufficient to meet my requirements.
Apache has solved their issues with ETAGs by appending the type of the variant
to the existing ETAG. For example, the ETAG for a gzip variant would have -gzip
appended (EG abc123 becomes abc123-gzip). This seems like a
Hi friends!
I have a question: How can I obtain the location path in http-handler which
handles requests intended to this location?
Here is what I mean:
http {
...
server {
...
location location_path { # I need
location_path value
...
}
...
}
...
}
Thanks
