Re: nginx-1.4 proxy requests being continious

2013-05-10 Thread Daniel Black
Just to prove I'm not making it up (even though I'm having a hard time replicating it). log_format extended '$remote_addr - $remote_user [$time_local] ' '"$request" $status $request_time $body_bytes_sent ' '$upstream_cache_status $upstream_addr $upstream_

Debian package

2013-05-10 Thread B.R.
Hello, Is Wheezy supported for Nginx? Would it be possible to use role-based package selection for the Nginx APT source? That means using: deb http://nginx.org/packages/debian/ *stable* nginx deb-src http://nginx.org/packages/debian/ *stable* nginx Instead of: deb http://nginx.org/packages/deb

async notification in Nginx

2013-05-10 Thread Alder Network
I am writing a Niginx module that from several of worker threads that I created by own, I need to notify Nginx's main thread so the main thread (single-threaded nginx) doesn't need to poll periodically in timer context. What would be the reliable way to do that in Nginx? Anybody advice would be app

Re: Proxying based on protocol (e.g. "ws"/"wss")?

2013-05-10 Thread Daniel Griscom
That's great information, but now I need to figure out how to selectively proxy to my websocket backend when $http_upgrade is "websocket". I see the following choices: 1) Have nginx listen at port 80, and proxy all traffic to port if $http_upgrade is "websocket", or port if not. Then

Re: Proxying based on protocol (e.g. "ws"/"wss")?

2013-05-10 Thread Maxim Dounin
Hello! On Fri, May 10, 2013 at 09:14:04AM +1200, Steve Holdoway wrote: > The scheme is available as... $scheme Yes, but WebSocket protocol uses http for handshake. So the scheme will be either "http" or "https". WebSocket requests can be identified based on Upgrade header, i.e. $http_upgrade