2008/10/10 Rob Walker <[EMAIL PROTECTED]>

> Anyone else found strange results moving to the Jetty 6 version of Http?
>
> It totally breaks our implementation, and seems to be directing
> getResource() requests to odd (possibly wrong) resource handlers
>
> We have both of the following aliases mounted for resource serving:
>
>   * /VtWebUi - served by a "WebUiContext" class
>   * /VtWebUi/logs - served by a "LogsContext" class
>
> A request to
>
>   http://localhost:8084/VtWebUi
>
> is getting directed to the LogsContext class (which serves /VtWebUi/logs) -
> and the attached resource path is empty
>
> According to my understanding (and the previous Jetty 4 version) - this
> should get directed to the "WebUiContext"
>
> This feels broken to me - a "general" alias shouldn't get routed to a
> context class with a specific qualifier on the end which doesn't match?
>

have you tried the same test with Pax-Web?  Alin spent a lot of time making
sure it followed the spec.


> Regards
>
> -- Rob
>
>
> Ascert - Taking systems to the Edge
> [EMAIL PROTECTED]
> +44 (0)20 7488 3470
> www.ascert.com
>



-- 
Cheers, Stuart

Reply via email to