Re: [Firebase] Firebase Long Polling blocked on strict firewalls

[Kato Richardson]

Hi Sean,

It's unclear what you mean by *.meetingpulseio.com being blocked. Could you explain how that pertains to realtime connections to the database?

As for proxying, you can't easily accomplish this. Sorry. The first hurdle here is that the SDKs will not connect to any URL that doesn't include the firebaseio.com domain. You'd need to modify the hosts files on the client machines or proxy network traffic to point to a different server, which is generally impractical.

☼, Kato

On Sat, May 14, 2016 at 9:56 AM, Sean Ganser <sean....@gmail.com> wrote:

We have a client with extremely high security. By default they've disabled websockets. When Firebase reverts to it's long polling solution, the url *.meetingpulseio.com is blocked in the client.

Does anyone know of a clever way to proxy Firebase so that all of the calls / bindings are done through our own server before hitting firebase? Whitelisting *.firebaseio.com is out of the question for our client, unfortunately.

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/efe36804-7c15-4dea-a07e-2780e1092fc5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Kato Richardson |

Developer Programs Eng |

kato...@google.com |

775-235-8398