Hi guys,
if you can create a testcase for me and provide apache config details -
I can try to reproduce and fix the issue on Glassfish.
Thanks.
WBR,
Alexey.
On 24.03.14 06:57, Jeanfrancois Arcand wrote:
> Salut,
>
> this is most probably an issue with GlassFish, not Atmosphere.
> Atmosphere doesn't handle the SSL stuff. I recommend you go to the
> Grizzly Mailing List to see if some issues has been found around that.
>
> Thanks
>
> -- Jeanfrancois
> On 2014-03-21, 5:26 PM, srinivas.jalagam_at_gmail.com wrote:
>> hi ,
>> I am also facing the same issue with apache 2.4.7 or 2.4.9 and tomcat
>> 8.0.10
>> I have posted earlier in the forum but no response..
>> looking for the root cause could not find with debugs.
>> thanks
>> srinivas
>>
>> On Thursday, March 20, 2014 9:30:41 AM UTC-7, sant..._at_gmail.com wrote:
>>
>> Hello there!
>>
>> We have the following configuration:
>> i) apache 2.4.9 on Windows 7 64bit configured to include:
>> proxy_module, proxy_http_module, proxy_wstunnel_module and
>> httpd-ssl.conf:
>> ProxyPass /efx-web/ ws://10.151.66.49:8090/efx-web/
>> <http://10.151.66.49:8090/efx-web/>
>> ProxyPassReverse /efx-web/ ws://10.151.66.49:8090/efx-web/
>> <http://10.151.66.49:8090/efx-web/>
>> ProxyPass /efx-web/ http://10.151.66.49:8090/efx-web/
>> <http://10.151.66.49:8090/efx-web/>
>> ProxyPassReverse /efx-web/ http://10.151.66.49:8090/efx-web/
>> <http://10.151.66.49:8090/efx-web/>
>> ii) atmosphere-runtime 2.1.1 + atmosphere-annotations 2.1.1
>> running on glassfish 3.1.2.2 + JRE 1.6.0 SR10 FP1 + AIX
>> 5300-12-06-1216,
>> iii) atmosphere client version 2.1.6 with configuration:
>> enableProtocol: true, transport: "websocket", fallbackTransport:
>> "streaming".
>>
>> Websockets via https work fine when glassfish IP is provided in
>> javascript client. One user interaction consists of:
>> i) first GET request with 'X-Atmosphere-tracking-id' header is
>> 200 OK,
>> ii) second GET request with Sec-WebSocket-Key,
>> Sec-WebSocket-Version and Upgrade headers is responded with 101
>> Switching protocols and the following headers:
>> Connection: Upgrade, Sec-WebSocket-Accept:
>> |exH2KfFJp0TaYS2R9XUeGVWaD0A=| and Upgrade: websocket.
>>
>> Websockets via https behind apache don't work:
>> i) first user interaction consists of one GET request. Data is sent.
>> ii) second user interaction consists of one GET request that is
>> missing headers: Sec-WebSocket-Key, Sec-WebSocket-Version, Upgrade.
>>
>> Any ideas?
>> Regards
>> Cezary
>>
>> --
>> Need support? http://async-io.org/subscription.html
>