Re: [jetty-user] Redirect to an http url when ssl handshake fails
Joakim Erdfelt <[email protected]> Fri, 22 Feb 2013 09:49:34 -0700
| Newsgroups | gmane.comp.java.jetty.support |
|---|---|
| Message-ID | <CAG4zZZCrKk-MdioVwZ=tdD8NBifMEV2wBg7dMVPBkv8UNO4Kmw@mail.gmail.com> |
--047d7b66fc19e2ca1604d652f93d Content-Type: text/plain; charset=ISO-8859-1 In order to send a redirect there has to be a HTTP conversation, as the redirect location is part of the HTTP response headers. But if the SSL handshake fails, there's no HTTP conversation. A little hard to send an HTTP response when there is no HTTP (yet) -- Joakim Erdfelt <[email protected]> webtide.com <http://www.webtide.com/> Developer advice, services and support from the Jetty & CometD experts eclipse.org/jetty - cometd.org On Fri, Feb 22, 2013 at 9:31 AM, Guillaume Bailleul <[email protected]>wrote: > Hi all, > > I am using jetty for a demonstration web application with smart card > identification. I have no problem using jetty with SSL with > authenticated client. > > When the smart card is disconnected and we try to load a page, the > handshake fails (as expected) and our browser shows an error page > specifying this failure. I would like to make jetty redirect to a > simple http url when the handshake fails, only to display a better > looking page. > > Is there a way to configure the jetty ssl connector to do that ? > > > Thanks for your help, > > Guillaume > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --047d7b66fc19e2ca1604d652f93d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable In order to send a redirect there has to be a HTTP conversation, as the red= irect location is part of the HTTP response headers.<div>But if the SSL han= dshake fails, there's no HTTP conversation.</div><div>A little hard to = send an HTTP response when there is no HTTP (yet)</div> <div><br clear=3D"all"><div><div>--</div><div>Joakim Erdfelt <<a href=3D= "mailto:[email protected]" target=3D"_blank">[email protected]</a>></d= iv><div><a href=3D"http://www.webtide.com/" target=3D"_blank">webtide.com</= a></div> <div><span>Developer advice, services and support</span><br><span>from the = Jetty & CometD experts</span></div><div><a href=3D"http://eclipse.org/j= etty/" target=3D"_blank">eclipse.org/jetty</a>=A0-=A0<a href=3D"http://come= td.org/" target=3D"_blank">cometd.org</a></div> </div> <br><br><div class=3D"gmail_quote">On Fri, Feb 22, 2013 at 9:31 AM, Guillau= me Bailleul <span dir=3D"ltr"><<a href=3D"mailto:[email protected]"= target=3D"_blank">[email protected]</a>></span> wrote:<br><blockqu= ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s= olid;padding-left:1ex"> Hi all,<br> <br> I am using jetty for a demonstration web application with smart card<br> identification. I have no problem using jetty with SSL with<br> authenticated client.<br> <br> When the smart card is disconnected and we try to load a page, the<br> handshake fails (as expected) and our browser shows an error page<br> specifying this failure. I would like to make jetty redirect to a<br> simple http url when the handshake fails, only to display a better<br> looking page.<br> <br> Is there a way to configure the jetty ssl connector to do that ?<br> <br> <br> Thanks for your help,<br> <br> Guillaume<br> <br> ---------------------------------------------------------------------<br> To unsubscribe from this list, please visit:<br> <br> =A0 =A0 <a href=3D"http://xircles.codehaus.org/manage_email" target=3D"_bla= nk">http://xircles.codehaus.org/manage_email</a><br> <br> <br> </blockquote></div><br></div> --047d7b66fc19e2ca1604d652f93d--