Re: Proxy issues

Ben, > I have now applied those changes you outlined above (I had before but the > way I did it, by leaving the old code there and commenting it didn't seem to > work from what you're saying) I've now applied the changes exactly as > outlined and rebuilt the server, is there anything else that I n

Re: Proxy issues

Ben, The errors in the log regarding 'Inbound closed before receiving peer's close_notify' and and the EOF are both normal and can be safely ignored. The stuff about SSL_NULL_WITH_NULL_NULL can also be safely ignored since that refers to the protocol used to setup the handshake when a connection i

Re: Proxy issues

Hey Ali, So I finally go my server setup using the SSL with the patches you mentioned here and I seem to be getting an error in the log... https://docs.google.com/open?id=0B5FF_Ld8SzsNa3dwY1gwakhkdzQ Feel free to have a look yourself, greycells.eu, the above log is one person logging in... Regard

Re: Proxy issues

Sorry, you are correct that the attachments don't go the list mailing list itself. I have put the files in my public dropbox space: Keytool: http://dl.dropbox.com/u/62577518/wave/keytool Server.config: http://dl.dropbox.com/u/62577518/wave/server.config Ali On 4 October 2012 12:06, Ben Hegarty

Re: Proxy issues

Hey Ali, I don't see you attachment of the config file, could you load it somewhere other than here, I think the groups attachements get striped off? Regards hegsie On Thu, Sep 27, 2012 at 4:29 PM, Ali Lown wrote: > Ben, > > Sure. I have attached my server.config (note that I mostly just tack >

Re: Proxy issues

Cheers, sounds like some investigation is in order :) Regards On Thu, Sep 27, 2012 at 4:29 PM, Ali Lown wrote: > Ben, > > Sure. I have attached my server.config (note that I mostly just tack > options on to the bottom as they get added to the WIAB code). > > I use iptables rules to move from 443

Re: Proxy issues

Ben, Sure. I have attached my server.config (note that I mostly just tack options on to the bottom as they get added to the WIAB code). I use iptables rules to move from 443 to 9898: -A PREROUTING -p tcp --destination 71.19.144.245 --dport 443 --j DNAT --to 71.19.144.245:9898 I use a StartSSL c

Re: Proxy issues

Hey Ali, I'm in the process of trying to set this up, is there any chance of seeing how the ssl cert and ports configuration that you used from the server.config file? Regards hegsie On Tue, Sep 25, 2012 at 10:33 AM, Ali Lown wrote: > Comet isn't really an option. > > The socket.io code is still

Re: Proxy issues

Comet isn't really an option. The socket.io code is still in the codebase, but if the browser is detected to have a websocket implementation they will be used instead. I was hoping to be able to remove the socket.io code soon since all major browsers now support websockets (ignoring IE<10). If y

Re: Proxy issues

Yep same as wave, firefox continually tries to authenticate and chrome just dies straight away, not that I know what it is but could we fall back to comet (because it seems to be ok) for situations like these? :( Bugger really wanted to be able to use wave, thanks again for all your help Ali, you'

Re: Proxy issues

So What happens in Firefox? Do you get asked to authenticate? On 25 Sep 2012 10:12, "Ben Hegarty" wrote: > 179664 > > On Tue, Sep 25, 2012 at 10:09 AM, Ali Lown wrote: > > > http://websocketstest.com >

Re: Proxy issues

What does http://websocketstest.com report? (Just link the report id) On 25 Sep 2012 10:07, "Ben Hegarty" wrote: > hmm I don't ever get an open connection in firefox, this doesn't seem to be > a problem other pages, i.e. gmail with GTalk works fine, facebook and all > the messaging there works fi

Re: Proxy issues

hmm I don't ever get an open connection in firefox, this doesn't seem to be a problem other pages, i.e. gmail with GTalk works fine, facebook and all the messaging there works fine too. The only time I've ever seen the authentication I got with wave is when I've had facebook open too long and I th

Re: Proxy issues

The firefox logs do show the attempts to authenticate (which is more than Chrome tries) at (say) #193,#194,#203,#204,#205,#213 which is a succesful login (I assume to open the connection for the page, since it is followed by #214 (TLSv1 Client Hello). The Websocket attempts (I think) look like #18

Re: Proxy issues

ok hopefuly this one is cleaner for firefox, though I have to add that firefox keeps asking for my credentials and no matter how many times I enter them it just keeps returning asking for them again... then after a while I just get a turbulence detected... https://docs.google.com/open?id=0B5FF_Ld8

Re: Proxy issues

In the chrome logs (original: #144, new: #344), in the firefox logs #274 show a 407 response to the attempt to CONNECT to wave.eezysys.co.uk:443. I would expect to possibly see a 407 once, at which stage the browser should then re-attempt the connection with the proxy credentials (as described her

Re: Proxy issues

Hey Ali, Was looking over the chrome capture and I'm not sure that the one below is very clean so I performed it again... https://docs.google.com/open?id=0B5FF_Ld8SzsNWG5rd0d0UnZVQU0 Regards hegsie On Tue, Sep 25, 2012 at 8:53 AM, Ben Hegarty wrote: > Hey Ali, > I've tested this again with fir

Re: Proxy issues

Hey Ali, I've tested this again with firefox to no avail... https://docs.google.com/open?id=0B5FF_Ld8SzsNaGFVV2NabEd0RFU and with chrome... https://docs.google.com/open?id=0B5FF_Ld8SzsNdmw5aThEZXF1U0k Regards hegsie On Mon, Sep 24, 2012 at 9:19 PM, Ben Hegarty wrote: > Ok, will do when I'm b

Re: Proxy issues

Ok, will do when I'm back behind the firewall tomorrow, I'll let you know how it goes. Cheers On Monday, September 24, 2012, Ali Lown wrote: > If you would like to test it again now/tomorrow? > > It took a few hours longer than I expected because I had to stop and > write a patch for Wave (and ha

Re: Proxy issues

line >> >> and >> >> >> no >> >> >> > wave data is saved down, you just see 'Unsaved all the time'.. >> >> >> > I've uploaded the wireshark trace to the following location :) >> >> >> > >> >> >

Re: Proxy issues

=0B5FF_Ld8SzsNMm5oOGJXajlOV00 > >> >> > > >> >> > HTH > >> >> > > >> >> > On Mon, Sep 24, 2012 at 4:33 PM, Ali Lown wrote: > >> >> > > >> >> >> > basically it looks like the problem comes from

Re: Proxy issues

On Mon, Sep 24, 2012 at 4:33 PM, Ali Lown wrote: >> >> > >> >> >> > basically it looks like the problem comes from the fact that the >> >> request >> >> >> > uses a relative path instead of a full path for the request >&g

Re: Proxy issues

> >> > > >> > On Mon, Sep 24, 2012 at 4:33 PM, Ali Lown wrote: > >> > > >> >> > basically it looks like the problem comes from the fact that the > >> request > >> >> > uses a relative path instead of a full path for

Re: Proxy issues

oks like the problem comes from the fact that the >> request >> >> > uses a relative path instead of a full path for the request >> >> >> >> AFAIK it is the browser's responsibility to convert relative paths for >> >> communicating to the

Re: Proxy issues

paths for > >> communicating to the server. > >> > >> > I've been investigating some issues that I've been having with using > wave > >> > behind a proxy server > >> > >> What are the actual problems you are having? Unable

Re: Proxy issues

ommunicating to the server. >> >> > I've been investigating some issues that I've been having with using wave >> > behind a proxy server >> >> What are the actual problems you are having? Unable to get 'Online' >> because the websocket doesn

Re: Proxy issues

r > communicating to the server. > > > I've been investigating some issues that I've been having with using wave > > behind a proxy server > > What are the actual problems you are having? Unable to get 'Online' > because the websocket doesn't get establi

Re: Proxy issues

at I've been having with using wave > behind a proxy server What are the actual problems you are having? Unable to get 'Online' because the websocket doesn't get established? > and found this thread about proxy issues which are > identical to the issue I'm seei

Proxy issues

Hey Guys, I've been investigating some issues that I've been having with using wave behind a proxy server and found this thread about proxy issues which are identical to the issue I'm seeing... https://bugs.eclipse.org/bugs/show_bug.cgi?id=107696 basically it looks like the problem