Hi, On Wed, Oct 10, 2018 at 7:36 PM Eze Ikonne <ike.iko...@aricent.com> wrote: > > Hi all, > > > > I just would like to report that I am making some progress on upgrading Jetty > 7 to Jetty 9.4.11, I will share the things that I have learned once the > effort is completed. However, I am now stuck because, for some reason, Jetty > 9.4.11 is returning a non-secure uri when it supposed to return secure uri > back to the browsers. My question is this, how do I indicate to Jetty 9.4.11 > to return a secure redirection uri instead of non-secure? Or, how does Jetty > 9.4.11 determine how to redirect to secure instead of non secure uri? Please > see the debug information generated by my jetty 9.4.11 below. I am almost > there towards the completion of this effort. As you can see, it is returning > a non secure uri for the location header attribute. My embedded Jetty 7 > correctly returns secure uri for the location header attribute. >
This is done with a SecureRequestCustomizer on the HttpConfiguration. Are you using it? -- Simone Bordet ---- http://cometd.org http://webtide.com Developer advice, training, services and support from the Jetty & CometD experts. _______________________________________________ jetty-users mailing list jetty-users@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
