In another thread, [EMAIL PROTECTED] wrote: > The way I read http://www.faqs.org/rfcs/rfc2396.html > section 3.3 > I don't believe the path segment can legally end with a '/'. > Read the RFC and see what you think. > So I don't believe http://www.google.com:80/?action=xyz > strictly speaking is valid, should we optionally allow for it > probably.
Something in or after the RequestProcessor is producing URL's with that same pattern (including /?) in my app. I asked on the users list and was told it didn't matter, but if that's really an invalid URL, perhaps someone could look into it. Here's the original thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg96484.html In the Action, I have: log.info("redirecting to: "+redirectURL); return new ActionForward( redirectURL, true ); The logs say: 15:53:45,640 - INFO edu.asu.vpia.struts.HarrisLoginAction - redirecting to: http://www.example.com?user=0123456 15:53:45,640 - DEBUG org.apache.struts.action.RequestProcessor - processForwardConfig(ForwardConfig[name=null,path=http://www.example.com ?user=0123456,redirect=true,contextRelative=false]) So I'm pretty sure there is no / after example.com, but what I see in the browser is: http://www.example.com/?user=0123456 Does anyone know where the extra '/' is coming from, or if it matters at all? -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
