El 07/03/13 11:04, Ali Lown escribió:
> Hi Puma,
>
> The wave codebase has lots of locations where it assumes that it has
> complete control of the domain it is set to. Attempting to put it in a
> sub-directory fails in the way that you have seen.
> The reason it assumes it is because the Jetty se
Hi Ali,
Thanks for the quick answer. For the moment, I'll move wave to a sub-domain.
Might look at the code later on, if I got some time, but I have little
experience with Java and none with Web Development...
Hi Puma,
The wave codebase has lots of locations where it assumes that it has
complete control of the domain it is set to. Attempting to put it in a
sub-directory fails in the way that you have seen.
The reason it assumes it is because the Jetty server believes it is running
without having any pro
I got the latest version of wave from the svn and the latest nginx (in
development) able to proxy websocket.
I set my wave config this way
http_websocket_public_address = mydomain.com:9898
http_frontend_public_address = mydomain.com:80/wave
http_websocket_presented_address = mydomain.com:80/wave
