Re: Decoded URL set on asynchronous request

2014-06-16 Thread Konstantin Kolinko
2014-06-16 22:38 GMT+04:00 Jimmy Royer : > On Sun, Jun 15, 2014 at 8:01 AM, Konstantin Kolinko > wrote: >> 2014-06-09 17:38 GMT+04:00 Konstantin Kolinko : >>> >>> (...) >>> >>> Servlet API javadocs: >>> http://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletRequest.html >>> >>> It does

Re: Decoded URL set on asynchronous request

2014-06-16 Thread Jimmy Royer
On Sun, Jun 15, 2014 at 8:01 AM, Konstantin Kolinko wrote: > 2014-06-09 17:38 GMT+04:00 Konstantin Kolinko : >> >> (...) >> >> Servlet API javadocs: >> http://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletRequest.html >> >> It does not mention explicitly whether getRequestURL() return

Re: Decoded URL set on asynchronous request

2014-06-15 Thread Konstantin Kolinko
2014-06-09 17:38 GMT+04:00 Konstantin Kolinko : > > (...) > > Servlet API javadocs: > http://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletRequest.html > > It does not mention explicitly whether getRequestURL() returns a > non-decoded or decoded URL, > > but as our implementation in o.

Re: Decoded URL set on asynchronous request

2014-06-10 Thread Mark Thomas
On 10/06/2014 00:12, Jimmy Royer wrote: > On Mon, Jun 9, 2014 at 9:38 AM, Konstantin Kolinko >> I think it is OK to file an issue into Bugzilla. >> >> Best regards, >> Konstantin Kolinko > > Thanks for your insights Konstantin. My understanding here is that there is an > ambiguous case if URLs

Re: Decoded URL set on asynchronous request

2014-06-09 Thread Jimmy Royer
On Mon, Jun 9, 2014 at 9:38 AM, Konstantin Kolinko wrote: > 2014-06-05 22:04 GMT+04:00 Jimmy Royer : >> Hello, >> >> I am using this combo of components: >> >> * Apache Tomcat 8.0.8 >> * Apache CXF 2.7.11 >> * Servlet 3.0 >> * JAX-RS 2.0 >> * JDK 1.7.0_45 >> * Windows 7 >> * Chrome browser with th

Re: Decoded URL set on asynchronous request

2014-06-09 Thread Jimmy Royer
On Mon, Jun 9, 2014 at 9:07 AM, Mark Thomas wrote: > On 09/06/2014 13:46, Jimmy Royer wrote: >> Is there any information that I should add to this to get some help? > > Right now, no. There may be further questions as folks dig into this. > >> Or should I just go straight and create a bug report f

Re: Decoded URL set on asynchronous request

2014-06-09 Thread Jimmy Royer
On Mon, Jun 9, 2014 at 9:00 AM, Daniel Mikusa wrote: > On Mon, Jun 9, 2014 at 8:46 AM, Jimmy Royer wrote: > >> Is there any information that I should add to this to get some help? >> > > Any chance you could put together a sample app or unit test to replicate > the problem? Ideally without third

Re: Decoded URL set on asynchronous request

2014-06-09 Thread Konstantin Kolinko
2014-06-05 22:04 GMT+04:00 Jimmy Royer : > Hello, > > I am using this combo of components: > > * Apache Tomcat 8.0.8 > * Apache CXF 2.7.11 > * Servlet 3.0 > * JAX-RS 2.0 > * JDK 1.7.0_45 > * Windows 7 > * Chrome browser with the Advanced REST Client plug-in > > I developed some web services using R

Re: Decoded URL set on asynchronous request

2014-06-09 Thread Mark Thomas
On 09/06/2014 13:46, Jimmy Royer wrote: > Is there any information that I should add to this to get some help? Right now, no. There may be further questions as folks dig into this. > Or should I just go straight and create a bug report for this (as this > might not be a message targeting the user

Re: Decoded URL set on asynchronous request

2014-06-09 Thread Daniel Mikusa
On Mon, Jun 9, 2014 at 8:46 AM, Jimmy Royer wrote: > Is there any information that I should add to this to get some help? > Any chance you could put together a sample app or unit test to replicate the problem? Ideally without third party components like CXF. It would make it easier someone on

Re: Decoded URL set on asynchronous request

2014-06-09 Thread Jimmy Royer
Is there any information that I should add to this to get some help? Or should I just go straight and create a bug report for this (as this might not be a message targeting the users mailing list but Tomcat's developers)? Thanks, Jimmy On Thu, Jun 5, 2014 at 2:04 PM, Jimmy Royer wrote: > Hello,