Hi Rob, To my mind, there is a problem in the current implementation. Before the tunnel checks the query, it decodes it using the UTF-8 character set by default. In case the tunnel has detected and filtered a query parameter, it computes a new query by removing the filtered query parameter. This new query is then encoded before being set to the request but without any character set. I wonder why no encoding has been defined.
Best regards, Thierry 2013/12/5 Thierry Boileau <tboil...@restlet.com> > Hello Rob, > > I have time today to check what happens. > > Best regards, > Thierry Boileau > > > 2013/12/2 Rob Elsner <r...@wowza.com> > >> I opened this issue; >> https://github.com/restlet/restlet-framework-java/issues/804 >> >> but I haven't heard anything back. >> >> I'm curious if anyone has an opinion on restlet and how the TUnnelFilter >> is re-encoding a + symbol. I think in this case the parameters are already >> decoded, so any + should have come from a %2b and should be re-encoded as a >> %2b, not a space (%20). This only happens when ?media= is used in the >> query parameters, if this is left out then the %2b is forwarded correctly >> to my controller. >> >> Thanks in advance, >> Rob >> >> ------------------------------------------------------ >> >> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3069588 >> > > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3069783
