Enable Pipelining in 0.6.35


#1

Hi

I did a few searches couldn’t find how to enable it in the stable
version.

Thanks…


#2

On Mon, Feb 9, 2009 at 4:10 PM, Nginx L. removed_email_address@domain.invalid wrote:

I did a few searches couldn’t find how to enable it in the stable
version.

Pipelining should be enabled in 0.6.x since it’s an HTTP/1.1 standard
feature. You can use the $pipe log variable to see which requests are
using it and which are not.


#3

I was experiencing some really weird behavior with Safari and thought it
could be related to the way Safari does it’s pipelining requests. Some
refreshes of the webpage would load some images , others with load other
images but no the ones it did previously. Has anyone experience similar
behavior ?

Cheers

Eden Li wrote:

On Mon, Feb 9, 2009 at 4:10 PM, Nginx L. removed_email_address@domain.invalid wrote:

I did a few searches couldn’t find how to enable it in the stable
version.

Pipelining should be enabled in 0.6.x since it’s an HTTP/1.1 standard
feature. You can use the $pipe log variable to see which requests are
using it and which are not.


#4

I’m looking at the logs and I’m not seeing the pipelined requests.
[10/Feb/2009:04:50:36 +0000] ."GET

I enabled pipelining in Firefox, still nothing.

Nginx L. wrote:

I was experiencing some really weird behavior with Safari and thought it
could be related to the way Safari does it’s pipelining requests. Some
refreshes of the webpage would load some images , others with load other
images but no the ones it did previously. Has anyone experience similar
behavior ?

Cheers

Eden Li wrote:

On Mon, Feb 9, 2009 at 4:10 PM, Nginx L. removed_email_address@domain.invalid wrote:

I did a few searches couldn’t find how to enable it in the stable
version.

Pipelining should be enabled in 0.6.x since it’s an HTTP/1.1 standard
feature. You can use the $pipe log variable to see which requests are
using it and which are not.


#5

Is there a way to disable pipelining in nginx ? Looks like the majority
of the browsers have it disable by default and IE7 doesn’t support it.

Thanks

Nginx L. wrote:

I’m looking at the logs and I’m not seeing the pipelined requests.
[10/Feb/2009:04:50:36 +0000] ."GET

I enabled pipelining in Firefox, still nothing.

Nginx L. wrote:

I was experiencing some really weird behavior with Safari and thought it
could be related to the way Safari does it’s pipelining requests. Some
refreshes of the webpage would load some images , others with load other
images but no the ones it did previously. Has anyone experience similar
behavior ?

Cheers

Eden Li wrote:

On Mon, Feb 9, 2009 at 4:10 PM, Nginx L. removed_email_address@domain.invalid wrote:

I did a few searches couldn’t find how to enable it in the stable
version.

Pipelining should be enabled in 0.6.x since it’s an HTTP/1.1 standard
feature. You can use the $pipe log variable to see which requests are
using it and which are not.


#6

keepalive_timeout 0;

disables pipelining and persistent connections.

Has anyone seen issues with safari where you get broken images as you
refresh.
From some testing it seems nginx is returning garbled data.

I will continue looking at the issue and provide tcp logs of the
communication.

Nginx L. wrote:

Is there a way to disable pipelining in nginx ? Looks like the majority
of the browsers have it disable by default and IE7 doesn’t support it.

Thanks

Nginx L. wrote:

I’m looking at the logs and I’m not seeing the pipelined requests.
[10/Feb/2009:04:50:36 +0000] ."GET

I enabled pipelining in Firefox, still nothing.

Nginx L. wrote:

I was experiencing some really weird behavior with Safari and thought it
could be related to the way Safari does it’s pipelining requests. Some
refreshes of the webpage would load some images , others with load other
images but no the ones it did previously. Has anyone experience similar
behavior ?

Cheers

Eden Li wrote:

On Mon, Feb 9, 2009 at 4:10 PM, Nginx L. removed_email_address@domain.invalid wrote:

I did a few searches couldn’t find how to enable it in the stable
version.

Pipelining should be enabled in 0.6.x since it’s an HTTP/1.1 standard
feature. You can use the $pipe log variable to see which requests are
using it and which are not.