Julian Sedding wrote > I have created SLING-5353[0] to track the failure of > WebDavDoubleSlashTest.testEmptyWorkspace and changed the test case so > that the response body is logged in case of a failure (see ticket for > output I have captured and formatted). > > Unfortunately I know too little about the scenario, so I cannot make > much sense from it. > Previous Http Jetty version was using a method which compacts "a//b" to "a/b". That's why we started getting the 404. This code is not executed anymore, and a//b stays like this - which gives us the old behaviour of Http Jetty 2.x.
Jetty standalone treats "a//b" as a different url as "a/b", so it seems the temporary behaviour of the last Http Jetty versions was wrong/unexpected. I'll fix the test case Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
