Re: URLEncoderImpl throws exception when resource has ablank

2013-06-24 Thread Thiago H de Paula Figueiredo
On Mon, 24 Jun 2013 05:36:56 -0300, John wrote: Yes the URLs have spaces, I don't think they should but I don't control that content. Still invalid URLs. I think this is related to TAP5-1803 https://issues.apache.org/jira/browse/TAP5-1803 Actually, it isn't. 1803 is about *valid* charac

Re: URLEncoderImpl throws exception when resource has ablank

2013-06-24 Thread John
vider to remove them! John - Original Message - From: Bob Harner To: Tapestry users Sent: Sunday, June 23, 2013 9:14 PM Subject: Re: URLEncoderImpl throws exception when resource has ablank Do the URLs in the request really have spaces? If so, they aren't valid and

Re: URLEncoderImpl throws exception when resource has ablank

2013-06-23 Thread Bob Harner
Do the URLs in the request really have spaces? If so, they aren't valid and should be encoded as + or %20 when the requests are being created. But if the spaces were encoded correctly then there is another isssue. On Jun 22, 2013 5:50 PM, "John" wrote: > Hi, > > I'm trying to use a page to serve

URLEncoderImpl throws exception when resource has ablank

2013-06-22 Thread John
Hi, I'm trying to use a page to serve static content. It works fine until a request for a resource name having blanks arrives, then this exception occurs. Is there a fix/workaround other than all resource names to not have spaces? John [ERROR] TapestryModule.RequestExceptionHandler Processing