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 comes from the fact that the request uses a relative path instead of a full path for the request GET /socket HTTP/1.1 Host: greycells.eu:9898 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-gb,en;q=0.5 Accept-Encoding: gzip, deflate DNT: 1 Sec-WebSocket-Version: 13 Origin: http://www.greycells.eu:9898 Sec-WebSocket-Key: kfLYCYXD7SDZFQ/Ia+L0Uw== Cookie: JSESSIONID=m304jmbg1f0a1v90z398pp4wt Pragma: no-cache Cache-Control: no-cache Upgrade: websocket Connection: Upgrade This GET here looks to be the source of the problem, I'm no network guy so it would be nice to have this confirmed by someone else, but do you think this would be a difficult fix? I have my own env for testing this so I could easily apply a patch and retest just need some help with the patch.. *(fingers crossed this is the issue)* Regards hegsie
