> 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
AFAIK it is the browser's responsibility to convert relative 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 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 seeing... > https://bugs.eclipse.org/bugs/show_bug.cgi?id=107696 This seems to be about eclipse's internal proxy settings handling being incorrect when it parses the relative URL. Assuming your browser is setup correctly the problem shouldn't lie with that. > 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)* The normal problem with websockets failing that I have seen, is when the proxy server doesn't understand (so drops) the UPGRADE request. Alternatively, it may well be the relative path, in which case the problem lies with your proxy server being incorrectly configured to handle them (since relative paths are most definitely part of RFC2616). What is the proxy server in question? It may be worth using wireshark to watch the actual request across the wire. Ali
