[weld-issues] [JBoss JIRA] Commented: (CDITCK-191) double slash in Conversation test urls break redirect

David Jencks (JIRA) jira-events at lists.jboss.org
Tue Nov 16 20:17:45 EST 2010


    [ https://jira.jboss.org/browse/CDITCK-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563726#comment-12563726 ] 

David Jencks commented on CDITCK-191:
-------------------------------------

I think it's unlikely I'll get approval from my employer to sign a CLA in a reasonable amount of time.  I apologize for supplying the patch without realizing a CLA was needed.  While I have a hard time imagining anyone could find copyrightable content in the patch, is there any chance someone can re-fix the problem without reference to the patch?

> double slash in Conversation test urls break redirect
> -----------------------------------------------------
>
>                 Key: CDITCK-191
>                 URL: https://jira.jboss.org/browse/CDITCK-191
>             Project: CDI TCK
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Tests
>    Affects Versions: 1.0.2.CR3
>            Reporter: David Jencks
>             Fix For: 1.0.3.CR4
>
>         Attachments: CDITCK-191.diff
>
>
> The Conversation tests all call AbstractConversationTest.getPath() with strings starting with / such as /storm.jspx.  Since the method tacks a / at the end of the context root you end up with urls for the form foo//bar.jsf.  While tomcat appears to think that this is the same url as foo/bar.jsf, jetty doesn't.  This breaks the redirect in LongRunningConversationPropagatedByFacesContextTest.testConversationPropagatedOverRedirect.
> Removing the / from the arguments to getPath fixes the problem.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the weld-issues mailing list