https://issues.apache.org/bugzilla/show_bug.cgi?id=55546
--- Comment #4 from Archie Cobbs <arc...@dellroad.org> --- > Adding HTTP upgrade support to AJP would be a task for Tomcat although > personally I'd say don't bother and proxy using HTTP instead. Unless I'm misunderstanding something, it appears that Tomcat already supports HTTP upgrade.. because it is responding with "101 Switching Protocols" and "Connection: upgrade". So maybe this is just an Apache limitation. > I'd expect to see some error messages in the Tomcat logs. No logs in error log. Access log shows: 127.0.0.1 - - [11/Sep/2013:09:23:22 -0500] "GET /demo3/PUSH/?v-uiId=6&v-csrfToken=4e90dd10-d18f-4c97-901c-fb8d98effe22&X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=1.0.14.vaadin4&X-Atmosphere-Transport=websocket&X-Atmosphere- TrackMessageSize=true&X-Cache-Date=0&Content-Type=application/json;%20charset=UTF-8 HTTP/1.1" 101 - Thanks. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
