I'm also getting this behaviour on Jetty.
If a pass a value with '%2' in it to the activation context it gets
translated into an empty string.


Fernando Padilla wrote:
> Wait.. so what is the expected/correct behavior??
>
> the url coming in is /%2Fblah/
>
> how should that be interpreted?
>
> and how can we make it so that it works on both jetty and tomcat?  Do
> you not have any unit tests for funky looking context values?
>
>
>
> Howard Lewis Ship wrote:
>> Ugh.  Jetty and Tomcat often disagree.  Jetty is always right, but
>> that doesn't help ... we end up having to patch for one or the other.
>>
>> On Thu, Feb 21, 2008 at 7:10 PM, Fernando Padilla <[EMAIL PROTECTED]>
>> wrote:
>>> So on further testing it looks like it works on production ( tomcat ),
>>>  but doesn't work on dev ( jetty ).  So sorry for the "fire alarm"
>>> tone;
>>>  it doesn't look to be anything about tapestry.
>>>
>>>  But I would still like some ideas to figure this out and make sure
>>> that
>>>  it won't bite me/us later.. :)
>>>
>>>  so it looks like if I include any slashes in a context parameter, it
>>>  gets encoded properly, but then gets unencoded once too many times by
>>>  jetty; thus interpreted as multiple context parameters.. totally
>>> messing
>>>  it up.
>>>
>>>  I am using Tapestry 5.0.11-SNAPSHOT (as of yesterday)
>>>
>>>
>>>
>>>
>>>
>>>  Fernando Padilla wrote:
>>>  > I have a url like this going into Tapestry.
>>>  >
>>>  >
>>> /fbracket/groups.canvaslayout.analyticsiframe:hbx/Groups/%2Ffbracket/M030
>>>
>>>  >
>>>  > And it's parsing it into the EventContext as:
>>>  >
>>>  > groups.canvaslayout.analyticsiframe:hbx; [ Groups, , fbracket,
>>> M030 ]; [
>>>  >  ] )
>>>  >
>>>  > So it's for some reason double decoding the url, and pulling out 4
>>>  > parameters instead of 3.
>>>  >
>>>  >
>>>  > Could someone please help?  I discovered this on production.. a
>>> little
>>>  > to late to pull it back out. :(
>>>  >
>>>  >
>>>
>>>  ---------------------------------------------------------------------
>>>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>  For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to