|Re: [jetty-users] Is this URI parsing bug?|
Hi, On Fri, Nov 20, 2015 at 11:47 AM, Tamás Cservenák <tamas@xxxxxxxxxxxxx> wrote: > Hi there, > > here is a simple test that makes Jetty 9.3.0 (tested with 9.3.5.v20151012) > puke 400 Bad URI, but IMHO that's wrong: > > https://gist.github.com/cstamas/90fc4b40a3cf9cb83ada > > The problem stems from here: > https://github.com/eclipse/jetty.project/blob/29722bd8803e76bbdbf70266cb9399560c10b712/jetty-http/src/main/java/org/eclipse/jetty/http/HttpURI.java#L303 > > As with HTTP req line like this > GET /@foo/bar HTTP/1.1 > > the HttpUri parses the "/@foo/bar" URI (in ctor), and it results as this at > parsing end: > > _scheme = null > _user = "/" > _host = null > _port = -1 > _path = "foo/bar" > _param = null > _query = null > _fragment = null > _uri = "" > _decodedPath = null > > Is this a bug? I think so, RFC 3986 allows non-percent-encoded "@" in the path (https://tools.ietf.org/html/rfc3986#appendix-A). Please raise a bugzilla at https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Jetty. Thanks ! -- Simone Bordet ---- http://cometd.org http://webtide.com Developer advice, training, services and support from the Jetty & CometD experts.
Back to the top