Hi
Thanks for your responses. Unfortunately, they don't seem to work.
> and then use the evil IF:
>
> if ($ios_ua) { keepalive_timout 0; }
This doesn't appear to work.
if ($http_user_agent ~ "^iOS/8\.") { keepalive_timeout 0; }
nginx: [emerg] "keepalive_timeout" directive is not allowed here
Due to a bug in iOS 8, I want to disable http keep-alive for all iOS 8
useragents for now.
https://github.com/AFNetworking/AFNetworking/issues/2314
I can't see a way to do this in nginx at the moment.
The docs for keep_alive disable only talk about msie6 and safari.
http://nginx.org/en/docs/ht
> > Yes, I haven't heard in a while what the status of this is. I'm
> > currently using our existing patch, but would love to drop it and
> > upgrade when it's included in nginx core...
>
> As far as I can tell the state is roughly the same (though patch
> in question improved a bit). Valentin?
> I have the same problem. I really need this feature. how is this going?
>
> >> Maxim Dounin:
> > Valentin is already worked on this, and I believe he'll be able to
> > provide a little bit more generic patch.
>
> does this mean in the future we can use epoll to detect the client
> connection'
> Valentin is already worked on this, and I believe he'll be able to
> provide a little bit more generic patch.
Ok, well I might just use ours for now, but won't develop it any
further.
Any idea on a time frame for this more official patch?
Rob
___
> > When an https client drops it's connection, the upstream http proxy
> > connection is not dropped. If nginx can't detect an https client
> > disconnect properly, that must mean it's leaking connection information
> > internally doesn't it?
>
> No. It just can't say if a connection was closed
> In case of https, in many (most) cases there are pending data -
> due to various SSL packets send during connection close. This
> means connection close detection with https doesn't work unless
> you use kqueue.
>
> Further reading:
>
> http://mailman.nginx.org/pipermail/nginx/2011-June/02
Hi
I'm trying to setup nginx to proxy a server sent events connection
(http://dev.w3.org/html5/eventsource/) to a backend server.
The approach is the browser connects to a particular path, which then
checks the cookies to see the connection is authorised, and then returns
an X-Accel-Redirect head
