PAXWEB-31 is resolved.

On 9/26/07, David Leangen <[EMAIL PROTECTED]> wrote:
>
> On Wed, 2007-09-26 at 18:06 +0800, Niclas Hedhman wrote:
> > On Wednesday 26 September 2007 16:39, David Leangen wrote:
> >
> > > Mainly, resources are not getting loaded correctly.
> > >
> > > Who's our main Pax Web guru around here?
> >
> > As Alin mentions, I think we are more compliant in this field
> (resources) than
> > Mr Hall. I think it boils down to we are explicitly dealing with the
> > resolution of aliases according to the OSGi spec, whereas I think
> > org.ungoverned just delegate the entire cycle to Jetty, which isn't
> exactly
> > the same as Osgi spec says.
> >
> > Now, this could mean that Pax Wicket have hacks adjusted to the
> org.ungoverned
> > behavior (bad, I know) and probably time to look at these again.
>
> My problem is related to http://issues.ops4j.org/jira/browse/PAXWEB-31.
>
>
> It seems that all the strange behaviours I am getting are related to
> this issue.
>
> So, maybe the problem is not so deep as I expected.
>
>
> Alin and I checked http and url specs, but found no mention of this.
> Seems that accepting extra slashes is by convention.
>
> For example, in apache, jetty, etc., the following are the same:
>
>   http://host/some/path
>   htpp://host///some////path
>
> In pax web, the first is ok, but the later gives a 404.
>
> Alin and I agree that we should follow conventions of other major apps.
>
> I believe Alin is working on fixing this now. 3 cheers for Alin! :-)
>
>
>
> Cheers,
>
> David
>
>
>
>
> _______________________________________________
> general mailing list
> general@lists.ops4j.org
> http://lists.ops4j.org/mailman/listinfo/general
>
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to