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 proxying magic being applied to it. We now have a lot of
http_* options to patch the code to support the various possibilities we
have seen so far:
- Websocket to a 'different' address
- Static files served from CDN
- iptables local port forwarding
- SSL/non-SSL usage
So, your options are now:
1) Fix the wave codebase :P
2) Use a subdomain instead, so that you can run wave at the root. e.g.
wave.domain.com/
Ali
On 7 March 2013 00:36, Puma Ingénieux <santania...@gmail.com> wrote:
> 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
> http_websocket_public_address = mydomain.com:9898
>
> And proxied things that come from mydomain.com:80/wave to
> mydomain.com:9898
>
> I can connect to the site, and log-in, I even get a status online... But I
> can`t see image and the client does not work.
>
> For some reason, it tries to get images :80/static instead of either
> :80/wave/static, or 9898/wave.
>
> Good I have some illumination on how to make it work at mydomain.com/wave.
>
> Here my current nginx config:
>
> location /wave/ {
> proxy_set_header X-Forwarded-Host $host;
> proxy_set_header X-Forwarded-Server $host;
> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> proxy_http_version 1.1;
> proxy_set_header Upgrade $http_upgrade;
> proxy_set_header Connection $connection_upgrade;
> # proxy_pass_header Upgrade;
> # proxy_pass_header Connection;
> proxy_pass http://domain.com:9898/;
> # return 403;
> }
>
>
> Thanks!
>
