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 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

I someone is interested I did some work on this some years ago:
http://code.google.com/r/vruizjurado-wiab-integration/source/detail?r=572e6f893f89898fb28239df577afb8ea7a99b02
but I didn't finish because it was not necessary for us finally. I
remember that was pending to patch socket-io in this direction.

BR,
-- 
Vicente J. Ruiz Jurado

http://comunes.org
http://ourproject.org
http://homes.ourproject.org/~vjrj/blog (@vjrj)

 "For the more there are who say 'Ours,'-not 'Mine'- by that much is
 each richer ." [Dante on the joys of sharing (Purgatorio, XV)]





Reply via email to