Thanks, I just tried this. It's still not coming online. I'm confused about.... I thought using apache2 for https is suppose to remove the need for jetty or other mod_proxy integrations like Tomcat to think in https. Apache2 is suppose to do the encrypt/decrypt work and jetty can just communicate in http. I guess the server has to at least tell the browser to make future requests in https so the redirect doesn't happen all the time.
Tad, do you have an idea what can be done here? What can I read to get some common sense about this? Thanks, On Wed, Mar 30, 2011 at 9:13 PM, David Hearnden <hearn...@google.com> wrote: > It looks to me like everything is working ok apart from the > socket.ioconnection. > > From looking at WebClient.java:232, it looks like the websocket connection > is to ws://..., which is for http, rather than wss://, which is for https. > > If you change: > ... return "ws" + ... > to > ... return "wss" + ... > does that make a difference? If that works, we can make the client > configurable for https. > > Tad Glines can probably give a more educated answer on how to get this > working. > > -Dave > > On Wed, Mar 30, 2011 at 5:16 AM, Scott Mitchell <smadirond...@gmail.com>wrote: > >> I set up wiab behind apache2 (www.familywave.org). It worked fine (online >> and federating) until I tried to get https to work. I'm able to login but >> do >> I need to do something with jetty to get this to work? I tried the >> following >> with no success: >> >> Configuring Apache mod_proxy with >> Jetty<http://docs.codehaus.org/display/JETTY/Configuring+mod_proxy>. >> >> I subclass SelectChannelConnector and override customize as it says but >> with not luck. Does anyone know what I'm missing? >> >> Thanks, >> >> Scott >> > >
