Hello!

On Mon, Jul 18, 2011 at 03:51:55PM +0100, Jürg Lehni wrote:

> That was exactly it!
>
> I knew it must be something really silly that I'm overseeing.
>
> Would it be good to mention this on the Wiki? I could imagine
> others having similar issues.
>
> It might be good also to allow the control of keepalive behavior
> separate for GET and POST requests?

The problem with Safari is that it may use any closed keepalive
connection to send POST and this will result in problems. That
is, the only way to mitigate the problem is to completely disable
keepalive connections with Safari.

Probably acceptable solution would be to change keepalive_disable
default to "msie6" (which would disable keepalives with old MSIE
after POSTs) leaving "safari" as a workaround option for people
who really use POSTs and see problems with Safari.

Maxim Dounin

>
> Thank you all for your help!
>
> Best,
>
> Jürg
>
> On 18 Jul 2011, at 15:08, Maxim Dounin wrote:
>
> > Hello!
> >
> > On Mon, Jul 18, 2011 at 02:48:47PM +0100, Jürg Lehni wrote:
> >
> >> This is very interesting! I just tried out Chrome and Firefox
> >> and I don't see these differences in performance. It's only on
> >> Safari. On Chrome, Nginx seems to have an edge even. How is this
> >> possible?
> >
> > This is probably due to disabled by default keepalive for Safari
> > due to problems with POSTs[1]. Try
> >
> > keepalive_disable msie6;
> >
> > (default is "msie6 safari")
> >
> > [1] https://bugs.webkit.org/show_bug.cgi?id=5760
> >
> > Maxim Dounin
> >
> > _______________________________________________
> > nginx mailing list
> > nginx@nginx.org
> > http://nginx.org/mailman/listinfo/nginx
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx