can you provide an example of using connect-gzip middle ware with proxy table

[haohello]

the only example for now I can find is the basic server with connect-gzip middle ware, thank you for your hard work.

[coderarity]

Yeah, I'll make a pull request for it.

[haohello]

Also, can you confirm that node-http-proxy works with socket.io flash transport? I was testing with IE for a site behind your http-proxy, it was complaining that the flash security policy file cannot be found, any ideas to work around this issue?

[coderarity]

From what I've read, Flash requires a socket policy to connect to the server. It should request for this on TCP port 843. You could try hosting this socket policy file on the proxy server (or proxy it to the Socket.io if it's an HTTP request).

You can read more about hosting socket policy file severs here.

On Friday, March 30, 2012 at 4:25 AM, haohello wrote:

Also, can you confirm that node-http-proxy works with socket.io flash transport? I was testing with IE for a site behind your http-proxy, it was complaining that the flash security policy file cannot be found, any ideas to work around this issue?

---

Reply to this email directly or view it on GitHub:
#212 (comment)

[haohello]

Hi there, thanks for prompt reply, from what I've found on both adobe website and socket io site, the default flash policy server is serving on port 843 the same as what you've observed, however there is a three-second timeout setting of requesting the policy file on port 843 of the server, if the browser cannot get the policy file after 3 second timeout, it'll resort to the default port of the server that you're requesting.

I tried to serve the policy file on port 843 and also the port 10843 (this is a default policy server port setting in socket.io), and it'll surely resolve my problem in this case, unfortunately this would create another problem, as usually is the case that major firewall software would block port 843 and 10843 (I've tested this on several of my computers here),

Since after the timeout the browser will try to request the policy file on the default requested port, as for all my socket.io apps, I'm using http-proxy for the reverse proxy and this http-proxy is listening on port 80, so I think it would be better off if we could serve the flash policy file on port 80 on the reverse proxy side, other than port 843 as which would normally be blocked and prevent the user from using the site any more.

[coderarity]

The thing is, if the request isn't on an HTTP or WebSocket protocol, I don't think it will be forwarded. I think that the policy file server doesn't use these protocols, but I'm not sure about that.

[haohello]

There is this npm package that may be able to give you some hints on how to work around, https://github.com/3rd-Eden/FlashPolicyFileServer

Also how the socket.io is using this package in its flash socket source is also a good pointer on this.
https://github.com/LearnBoost/socket.io/blob/master/lib/transports/flashsocket.js