Re: Using both keepalive requests and timeout

Hi All, I have a query, I tried setting keep alive_timeout to a non-zero value and found it not working correctly. Are there any related parameters for this? //Jagannath From: "Valentin V. Bartenev" mailto:vb...@nginx.com>> Organization: NGINX, Inc. Reply-To: "nginx@nginx.org

Re: Technical reason behind client_body_temp_path

On Wednesday 19 November 2014 16:56:41 attozk wrote: > I am trying to understand the reason for buffering incoming request > (client_body_buffer_size) in which nginx would either keep request in memory > or write to file client_body_temp_path (based on request size). > > What are the performance a

Re: Rewrite with permanent and last

On Wed, Nov 19, 2014 at 2:44 PM, Francis Daly wrote: > On Wed, Nov 19, 2014 at 02:37:11PM -0800, neubyr wrote: > > Hi there, > > > Is it possible to rewrite URL with HTTP 301 and make that last rule in > > current ruleset? > > Is that not what the flag "permanent" does? > > http://nginx.org/r/rew

Re: Rewrite with permanent and last

On Wed, Nov 19, 2014 at 02:37:11PM -0800, neubyr wrote: Hi there, > Is it possible to rewrite URL with HTTP 301 and make that last rule in > current ruleset? Is that not what the flag "permanent" does? http://nginx.org/r/rewrite If not, can you show the config snippet, the request you make, an

Rewrite with permanent and last

Is it possible to rewrite URL with HTTP 301 and make that last rule in current ruleset? For example, in apache one can use flags "[R=301,L]" , but how can one do it in nginx? I tried using following, but it returned syntax error: Config: rewrite /members /users permanent last; Error: nginx: [emer

Technical reason behind client_body_temp_path

I am trying to understand the reason for buffering incoming request (client_body_buffer_size) in which nginx would either keep request in memory or write to file client_body_temp_path (based on request size). What are the performance advantages and/or technical challenges to such an approach as op

How to extract multiple values of a header for logging

I have a custom header in http response and it can appear more than once. Let's say it is called x-extra. In my nginx configuration, I want to extract all of its values and log them together but I found it is always extracting the very first one. Is it possible to do this somehow? Thanks in adv

Re: Using both keepalive requests and timeout

On Wednesday 19 November 2014 14:52:19 josephlim wrote: > Hi Valentin, > > Thank you for clarifying that, however now that makes me wonder about this: > if we set our timeout value to 30s and did not set our requests value, does > this mean that the default requests value of 100 restriction is imp

Re: Using both keepalive requests and timeout

Hi Valentin, Thank you for clarifying that, however now that makes me wonder about this: if we set our timeout value to 30s and did not set our requests value, does this mean that the default requests value of 100 restriction is imposed or does nginx only respect the timeout value explicitly decla

Re: Using both keepalive requests and timeout

On Wednesday 19 November 2014 14:30:59 josephlim wrote: > Hi all, > > I was curious to see if anyone used both keepalive_requests and > keepalive_timeout at the same time and knew the expected behaviour? I was > hoping that nginx would do whichever conditions were met first. > Yes, you're right.

Using both keepalive requests and timeout

Hi all, I was curious to see if anyone used both keepalive_requests and keepalive_timeout at the same time and knew the expected behaviour? I was hoping that nginx would do whichever conditions were met first. Thank you very much in advance. Posted at Nginx Forum: http://forum.nginx.org/read.ph

Re: Integrating softHSM with nginx

Hello! On Wed, Nov 19, 2014 at 01:15:46PM -0500, sandeepkolla99 wrote: > Thank you very much for the your quick response. Could you please tell me > the approximate time period when it is going to be committed?. No ETA. -- Maxim Dounin http://nginx.org/ ___

Re: Integrating softHSM with nginx

Thank you very much for the your quick response. Could you please tell me the approximate time period when it is going to be committed?. Regards, Sandeep Posted at Nginx Forum: http://forum.nginx.org/read.php?2,254902,254945#msg-254945 ___ nginx maili

Re: nginx configuration - sharetronix

On Mon, Nov 03, 2014 at 01:40:33AM -0500, Replace wrote: Hi there, > i try to setup sharetronix on my vps server, with nginx + php5-fpm. The > problem is (maybe) my nginx configuration, when i try to view website, i get > error 404 - No input file specified. What request do you make, and what re

Re: Integrating softHSM with nginx

Hello! On Tue, Nov 18, 2014 at 06:03:46PM -0500, sandeepkolla99 wrote: > Hii friends, > >I want to integrate softHSM with nginx. I did not find any resource > to make it working. I found two below links from Nginx developement forum. > But, They are not helpful to me. I'm trying to int

config file syntax: is there a formal definition?

I like to see something like BNF (http://en.wikipedia.org/wiki/Extended_Backus%E2%80%93Naur_Form) describing the configuration file language. Anyone created such a list? thanks Noam Posted at Nginx Forum: http://forum.nginx.org/read.php?2,254935,254935#msg-254935 __

Re: Have full URL redirect to SSL (not just $server_name and $request_uri)

That seems to be just the ticket -- thankyou very much! Posted at Nginx Forum: http://forum.nginx.org/read.php?2,254914,254933#msg-254933 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: nginx configuration - sharetronix

Bump* :) Posted at Nginx Forum: http://forum.nginx.org/read.php?2,254533,254931#msg-254931 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Incomplete HTTP request body sent to upstream

Hello! On Wed, Nov 19, 2014 at 02:13:41PM +0100, Roman Borschel wrote: > Hi, > > I'm experiencing an issue whereby nginx and the upstream server get into > disagreement about the state of the HTTP interaction, apparently caused by > nginx not transmitting the complete request body. The scenario

Re: Integrating softHSM with nginx

Can someone please respond to my request?. Regards, Sandeep Posted at Nginx Forum: http://forum.nginx.org/read.php?2,254902,254930#msg-254930 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Have full URL redirect to SSL (not just $server_name and $request_uri)

On Wed, Nov 19, 2014 at 11:22 PM, biot023 wrote: > Ah, will do, cheers -- I had a look through the NGINX variables, but it > wasn't really clear which variable did what. > I suppose something like: > > location / { > return 301 https://$uri; > } > > Wouldn't work? > generic redirect looks like

Re: Have full URL redirect to SSL (not just $server_name and $request_uri)

Ah, will do, cheers -- I had a look through the NGINX variables, but it wasn't really clear which variable did what. I suppose something like: location / { return 301 https://$uri; } Wouldn't work? Posted at Nginx Forum: http://forum.nginx.org/read.php?2,254914,254922#msg-254922

intermittent problems reaching files (whether served via php or not)

having difficulty to serve simple video files here (for playback in a browser via video-js or other player). even without the video player there are problems. i have tested access to the video file both when the file is served from within the php framework i am using (elgg.org) and also directly fr

Re: problem with argument route in upstream

Thanks I am going to have a look on this module Envoyé de mon iPhone > Le 19 nov. 2014 à 09:44, mex a écrit : > > Hi, > > you can use the nginx-sticky-module if you need sticky sessions > https://bitbucket.org/nginx-goodies/nginx-sticky-module-ng > > it just has no way to extract the routing

Incomplete HTTP request body sent to upstream

Hi, I'm experiencing an issue whereby nginx and the upstream server get into disagreement about the state of the HTTP interaction, apparently caused by nginx not transmitting the complete request body. The scenario is as follows, using nginx as a reverse proxy with upstream keepalive: 1. Client s

Re: chunked_transfer_encoding seems doesn't work as expected

Hello! On Wed, Nov 19, 2014 at 08:49:33PM +0800, weiyuefei wrote: > When i try to use the directive "chunked_transfer_encoding" to > control the encoding type of output data, it failed to output > the chunked data even thougth i turned on the directive as > "chunked_transfer_encoding on;". Th

chunked_transfer_encoding seems doesn't work as expected

Hi All, When i try to use the directive "chunked_transfer_encoding" to control the encoding type of output data, it failed to output the chunked data even thougth i turned on the directive as "chunked_transfer_encoding on;". Here is the simple example of my config==> location /chunked {

Re: Have full URL redirect to SSL (not just $server_name and $request_uri)

On Wed, Nov 19, 2014 at 9:16 PM, biot023 wrote: > Hi -- we currently have a redirect rule in a location on our server to > redirect all non-SSL traffic to SSL, like so: > > location / { > return 301 https://$server_name$request_uri; > } > > This works for almost all cases, but there is an edge c

Have full URL redirect to SSL (not just $server_name and $request_uri)

Hi -- we currently have a redirect rule in a location on our server to redirect all non-SSL traffic to SSL, like so: location / { return 301 https://$server_name$request_uri; } This works for almost all cases, but there is an edge case that is broken by this. We have a custom subdomain function

Re: Slow Time to first byte

Should I have posted this in the fpm mailing list? Posted at Nginx Forum: http://forum.nginx.org/read.php?2,254876,254913#msg-254913 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: "110: Connection timed out" and "104: Connection reset by peer" error in nginx error log

Short answer: Not nginx-related (you are on the nginx mailing list). Long answer: As your log clearly indicates, your upstream sometimes fails either by resetting connections improperly or even by not accepting them at all. Everything indicates your backend does not sustain the load. The most tro

"110: Connection timed out" and "104: Connection reset by peer" error in nginx error log

Hi All, When i run my Jmeter load test with 2000 users ,I got below 2 error in nginx error log frequently. /opt/nginx/logs/error.log=> 2014/11/06 11:05:40 [error] 3430#0: *18263 connect() failed (110: Connection timed out) while connecting to upstream, client: 54.176.137.82, server: proteus.io,

Re: Slow Time to first byte

so it looks more like a php/processing-problem, no? cheers, mex Posted at Nginx Forum: http://forum.nginx.org/read.php?2,254876,254910#msg-254910 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: problem with argument route in upstream

Hi, you can use the nginx-sticky-module if you need sticky sessions https://bitbucket.org/nginx-goodies/nginx-sticky-module-ng it just has no way to extract the routing-info from tomcat-routes (yet, we're working on it) and comes with an own cookie, but is production-ready cheers, mex Post