Escaping them won't work unless TextParseUtils is changed, for example
assume this is submitted: name=%{name}
we scape %{name} to '%{name}', when TextParseUtils "sees" the %{...} will
try to expand it (we would have to check for single quotes around %{}).
In the meanwhile I submitted a patch to the issue for those that need a
quick fix (until a real fix is made), parameters that match the regex
.*?%\{.*?\} won't be accepted. This regex is configured as a parameter to
the params Interceptor.
musachy
On 7/5/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
I that case we would have to scape back the strings at some point.
muachy
On 7/5/07, Antonio Petrelli < [EMAIL PROTECTED]> wrote:
>
> 2007/7/5, Musachy Barroso < [EMAIL PROTECTED]>:
> > The thing is that there isn't (that I see) any way to know if a value
> was
> > passed by the user.
>
> What about escaping the strings, then?
>
> Antonio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
