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

[Pete Muir (JIRA)]

     [ https://issues.jboss.org/browse/CDITCK-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir closed CDITCK-191.
----------------------------

    Resolution: Done


Hi David, unfortunately we don't have the resources to maintain multiple exclude lists, and so only maintain exclude lists against the latest released (final) TCK. I just cleared out the exclude list since we just releaed 1.0.2.Final (SP1 as well actually).

We are looking at ways of maintaining full exclude lists in the future.

> double slash in Conversation test urls break redirect
> -----------------------------------------------------
>
>                 Key: CDITCK-191
>                 URL: https://issues.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
>            Assignee: Pete Muir
>             Fix For: 1.1.0.CR1, 1.0.3.Final
>
>         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