https://issues.apache.org/bugzilla/show_bug.cgi?id=55546
--- Comment #6 from Archie Cobbs ---
> > So maybe this is just an Apache limitation.
>
> No, it is also an AJP limitation and that protocol is owned by the Tomcat PMC.
Thanks, now I understand. So in the packet trace, AJP is simply passin
https://issues.apache.org/bugzilla/show_bug.cgi?id=55546
--- Comment #5 from Mark Thomas ---
(In reply to Archie Cobbs from comment #4)
> Unless I'm misunderstanding something, it appears that Tomcat already
> supports HTTP upgrade.. because it is responding with "101 Switching
> Protocols" and
https://issues.apache.org/bugzilla/show_bug.cgi?id=55546
--- Comment #2 from Archie Cobbs ---
Thanks for the clarification.
What would be the appropriate next step then? Would getting this to work
constitute a feature request for Apache httpd, or Tomcat, or both?
FYI, the upgrade request does p
https://issues.apache.org/bugzilla/show_bug.cgi?id=55546
--- Comment #4 from Archie Cobbs ---
> 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 alr
https://issues.apache.org/bugzilla/show_bug.cgi?id=55546
--- Comment #3 from Mark Thomas ---
(In reply to Archie Cobbs from comment #2)
> What would be the appropriate next step then? Would getting this to work
> constitute a feature request for Apache httpd, or Tomcat, or both?
I'd expect proxy
https://issues.apache.org/bugzilla/show_bug.cgi?id=55546
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
