Interesting, not sure that there are any browsers that support this flow. The SSL negotiation between the client and server at this point in time would be tricky. You are definitely in the realm of a custom HTTP client at this point. Wish you the best of luck, let us know how it goes.
-- Joakim Erdfelt On Tue, Sep 25, 2012 at 9:55 AM, Manfred <[email protected]> wrote: > Thanks Simon. > > I've looked through the classes and how possibly the "upgrade" could work. > However I'm not sure this is the right way of doing things. > I would: > > - check for "Upgrade" header in Servlet's service() method > - if "Upgrade" create a SslConnection > - send a "101 Switching Protocol" response > - change the connection object via: > request.setAttribute("org.eclipse.jetty.io.Connection", sslConnection) > > Would this be a viable route? > Would Jetty handle everything from there on for me? > > > > Regards, > Manfred > > > > -- > View this message in context: > http://jetty.4.n6.nabble.com/jetty-users-Jetty-and-Http-1-1-upgrade-header-tp4959222p4959235.html > Sent from the Jetty User mailing list archive at Nabble.com. > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
