> It looks like the connection is being fully established fine. Does it work
> if you disable websockets (ie. does it work with just jsonp-polling enabled
> as a transport?)

> Eric

> On Mon, Jan 2, 2012 at 3:31 PM, james33 <jame...@gmail.com> wrote:
> > No, there's no errors or warnings on either end. This is the
> > connection info pulled from Chrome:http://i.imgur.com/pKQaj.jpgand
> >http://i.imgur.com/yAXBS.jpg.

> > Maybe I'm setting it up wrong? I'm including
> >http://socket.domain.com/nowjs/now.js
> > onhttp://domain.com/app. This works without issue if I include
> >http://domain.com/nowjs/now.jsinstead, and the only difference I see
> > between the 2 files is on the last line with the subdomain.

> > On Jan 2, 3:36 pm, Eric Zhang <e...@nowjs.com> wrote:
> > > Ok I see.

> > > Are there any errors or warnings printed on either the server or the
> > client?

> > > On Mon, Jan 2, 2012 at 12:52 PM, james33 <jame...@gmail.com> wrote:
> > > > It doesn't, but it will work with websockets if you use a subdomain
> > > > that isn't using the CloudFlare proxy. When I setup NowJS to use the
> > > > subdomain, it is able to make the connection, but none of the client-
> > > > side functions on now get called (so the socket connection is made
> > > > through socket.domain.com, and the client is seeing just domain.com).

> > > > On Dec 31 2011, 4:52 am, Eric Zhang <e...@nowjs.com> wrote:
> > > > > Hi James,

> > > > > NowJS works fine with crossdomain and crossport configurations,
> > however
> > > > the
> > > > > issue is likely that the CloudFlare proxy is unable to forward
> > websocket
> > > > > connections (I am not actually sure, haven't tried but that is a
> > common
> > > > > issue with many reverse proxies).

> > > > > You want to explicitly disable websockets and give it a try:

> > > > > `nowjs.initialize(httpServer, {socketio: {transports: ['xhr-polling',
> > > > > 'jsonp-polling']}});`

> > > > > Eric

> > > > > On Thu, Dec 29, 2011 at 1:11 PM, james33 <jame...@gmail.com> wrote:
> > > > > > I'm trying to use CloudFlare with my Node/NowJS app, but since
> > > > > > CloudFlare acts as a proxy, web-sockets won't work directly. The
> > only
> > > > > > way to make them work is to do them on a subdomain that isn't
> > routed
> > > > > > through CloudFlare, so I setup a socket.domain.com subdomain to
> > do the
> > > > > > web-socket connection with. I then changed the last line of now.js
> > to
> > > > > > use the subdomain, but it doesn't seem to work. The socket.io
> > > > > > connection seems to be established fine, but nothing in the now
> > > > > > namespace seems to work now. Is this just not possible, or am I
> > doing
> > > > > > it wrong?

> > > > > --
> > > > > Co-Founder @ Flotype, makers of NowJS

> > > --
> > > Co-Founder @ Flotype, makers of NowJS

> --
> Co-Founder @ Flotype, makers of NowJS