Hello Chris, I think I misread your message, sorry. So the request attribute javax.servlet.forward.request_uri contained a URL starting with // , right?
Do you have the initial http request, how it looks like? Greetings, Thomas > ________________________________ > Von: Christopher Schultz <ch...@christopherschultz.net> > Gesendet: Mittwoch, 24. August 2022 20:15:25 > An: Tomcat Users List > Betreff: Unexpected double-slash in javax.servlet.forward.request_uri > > All, > > I haven't tried narrowing this down very much yet, but I have a situation > where > I'm using javax.servlet.forward.request_uri to build a URI and the string I'm > pulling from there starts with TWO / characters instead of one. > > This ends up breaking navigation because the browser interprets this as a > protocol-relative URI instead of a host-relative URI and Bar Things happen. > > Has anyone ever seen anything like this? > > Tomcat 8.5.latest. > > -chris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -----Ursprüngliche Nachricht----- > Von: Thomas Hoffmann (Speed4Trade GmbH) > <thomas.hoffm...@speed4trade.com.INVALID> > Gesendet: Donnerstag, 25. August 2022 10:48 > An: Tomcat Users List <users@tomcat.apache.org> > Betreff: AW: Unexpected double-slash in javax.servlet.forward.request_uri > > Hello Chris, > > I think it matches the RFC7231 > https://www.rfc-editor.org/rfc/rfc7231#section-7.1.2 > > It allows relative URLs which refers to: > https://www.rfc-editor.org/rfc/rfc3986#section-4.2 > > Which allows protocol relative paths: > relative-part = "//" authority path-abempty > / path-absolute > / path-noscheme > / path-empty > > Greetings, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
