Hi,
> Any ideas?
Your client is using TLS Session Tickets (client-side caching), so
nginx-side cache isn't used for that sessions.
Best regards,
Piotr Sikora
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi,
This is an example of an entry in the log, left by HttpLimitReqModule:
2013/10/27 10:00:11 [error] 1402#0: *313355 limiting requests, excess: 0.580
by zone "zone1", client: 20.147.43.103, server: api.acme.com, request: "GET
/location/locate-ip?key=&ip=85.210.42.204 HTTP/1.1", host:
"api.a
How do we use CAS login screen to authenticate Nginx.
We have deployed front end using EXT JS in Nginx server and Nginx server is
using reverse proxy to get the data from JBOSS server (spring MVC rest
services).
We have deployed Jasig CAS application in tomcat server and configured our
JBOSS serv
spdy/2 support has been removed from the Firefox code base (
https://bugzilla.mozilla.org/show_bug.cgi?id=912550 ) and >= Firefox 27 will
only support >= spdy/3. Firefox 27 will be released in January 2014 (
https://wiki.mozilla.org/RapidRelease/Calendar ) so there is some urgency in
getting spdy/3
For nearly 50 years,
[url=http://www.pandoracharmscanadaonline2013.org/pandora-jewelry-1/pandora-charms.html]pandora
charms[/url] is quietly carried out a revolution, and imperceptibly changing
the jewelry industry. A new way of thinking has taken a new atmosphere and
charm to the fashion jewelry.
On Mon, Oct 28, 2013 at 09:36:20AM +0100, Ingo Schmidt wrote:
Hi there,
I was (partly) wrong when I said
"""
> I guess that the URL encoding also takes place in the first case, but
> here the client decodes the URL and thus everything is ok again.
No; here what is sent to the client includes t
Hi!
I believe it is intended to be "no", for internal rewrites at least.
Hmm, any reason why it might be intended?
Also, it would be nice if the docs could mention this, because I find it
unintuitive, if rewrite behaves differently depending on the rewrite type.
You can do something like set
On Mon, Oct 28, 2013 at 01:56:16AM +0100, Ingo Schmidt wrote:
Hi there,
> set $var "/url?par=val";
> location = /b {
> rewrite ^ $var last;
> }
> For location b the redirect is internal and now the backend cannot
> process the request anymore.
> I guess that the URL encoding also takes pla
Nginx has actually no support for the 429 code. Either you fix it by
proposing a patch to support the error page in core or you use an
error_page directive.
error_page 429 @toomany;
location @toomany {
return 429 'Too many requests.\n';
}
Just a simple example.
Le 28 oct.
