nginx stores static prefix locations in some kind of binary tree. This means
that
lookup is fast enough AND the order of the locations does not matter at all.
The latter allows to create a lot of easy maintainable locations.
Regex locations are processed in the order of appearance. This is slow a
Maxim Dounin Wrote:
---
> Hello!
>
> On Tue, Feb 18, 2014 at 02:58:05PM -0500, atarob wrote:
>
> > The config listen option rcvbuf which maps to the TCP SO_RCVBUF, is
> applied
> > to the listening socket, and not inherited by the accept()ed
> c
On Tue, Feb 18, 2014 at 2:51 PM, atarob wrote:
> Pankaj Mehta Wrote:
> ---
>> These should be covered during the link time optimisations.
>>
>> Look here for gcc: http://gcc.gnu.org/wiki/LinkTimeOptimization
>
> I was very much unaware of this. T
Hello!
On Tue, Feb 18, 2014 at 02:58:05PM -0500, atarob wrote:
> The config listen option rcvbuf which maps to the TCP SO_RCVBUF, is applied
> to the listening socket, and not inherited by the accept()ed connections. So
> if you have a high load application where the legitimate request is bound t
Hello,
I want something like limit_except functionality but based on custom request
headers. Lets say I have a Request header X-Secured-Client set. In that case
only I want to allow the request to my upstream server.
How can I achieve that without using "if" blocks? (I did search the mailing
lis
The config listen option rcvbuf which maps to the TCP SO_RCVBUF, is applied
to the listening socket, and not inherited by the accept()ed connections. So
if you have a high load application where the legitimate request is bound to
be no more than 4K, for instance, you could save a lot of RAM by drop
Pankaj Mehta Wrote:
---
> These should be covered during the link time optimisations.
>
> Look here for gcc: http://gcc.gnu.org/wiki/LinkTimeOptimization
I was very much unaware of this. The linker actually compiles. Wow.
Thanks.
Posted at
Maxim Dounin Wrote:
---
> Hello!
>
> On Fri, Feb 14, 2014 at 04:39:23PM -0500, atarob wrote:
>
> > Creating a module, I want to read in from config desired http header
> fields.
> > Then, during config still, I want to get the struct offset for
Are there any performance implications associated with having a large number of
static prefix locations? We really are looking at having hundreds of location
blocks per server if we use static prefixes, and my primary concern up until
now has been maintainability. If I eliminate maintainability
On Tuesday 18 February 2014 09:54:40 p.heppler wrote:
> Another run with Tomcat, fresh log:
[..]
In both cases your backend returned a "200 OK" response
with empty body:
2014/02/18 15:46:13 [debug] 12839#0: *2 http proxy status 200 "200 OK"
2014/02/18 15:46:13 [debug] 12839#0: *2 http proxy heade
Another run with Tomcat, fresh log:
2014/02/18 15:58:53 [debug] 12993#0: epoll add event: fd:9 op:1 ev:2001
2014/02/18 15:58:57 [debug] 12993#0: post event 7F19759D4078
2014/02/18 15:58:57 [debug] 12993#0: delete posted event 7F19759D4078
2014/02/18 15:58:57 [debug] 12993#0: accept on
I meanwhile replaced Tomcat with Jetty, because Jetty also supports SPDY.
But same result.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,247692,247696#msg-247696
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinf
I just created a new log. This is from nginx restart to first request:
2014/02/18 15:45:56 [debug] 12839#0: epoll add event: fd:9 op:1 ev:2001
2014/02/18 15:46:12 [debug] 12839#0: post event 7F29CC9D1078
2014/02/18 15:46:12 [debug] 12839#0: delete posted event 7F29CC9D1078
2014/02/18 1
On Tuesday 18 February 2014 09:15:25 p.heppler wrote:
> Hello,
> I compiled nginx 1.5.10 on Centos 6.5 and try to use it as frontend for
> Tomcat.
> If I use pure SSL everything works fine. But as soon as I enable SPDY, I
> only get a blank page.
> And Content-Length Header is 0, but HTTP status co
Hello,
I compiled nginx 1.5.10 on Centos 6.5 and try to use it as frontend for
Tomcat.
If I use pure SSL everything works fine. But as soon as I enable SPDY, I
only get a blank page.
And Content-Length Header is 0, but HTTP status code is 200.
But, the blank page only affects request which are hand
Hello!
On Mon, Feb 17, 2014 at 09:26:56PM +, Brian Hill wrote:
> So there is no precedence given to nested regex locations at
> all? What value does nesting provide then?
Nesting is to do thins like this:
location / {
# something generic stuff here
location ~ \.jpg$ {
16 matches
Mail list logo
