https://issues.apache.org/jira/browse/TAP5-1803
Done!
Regards
------------------------------------------------------------------
David Germán Canteros
2011/12/22 Lenny Primak <lpri...@hope.nyc.ny.us>
> Thanks for confirming this. It is definitely a bug. Please file an JIRA
> issue.
>
> On Dec 22, 2011, at 4:21 PM, David Canteros wrote:
>
> > You are right... thanks again! According to the UrlEncoderImpl the safe
> > chars are the following:
> >
> > * private final BitSet safe = new BitSet(128);
> >
> > {
> > markSafe("abcdefghijklmnopqrstuvwxyz");
> > markSafe("ABCDEFGHIJKLMNOPQRSTUVWXYZ");
> > markSafe("01234567890-_.:");
> > }
> > *
> > I dont know the internal working of Tapestry that have this requirement,
> > but it should consider that some applications follow the standard, al
> least
> > with @ActivationRequestParameter.
> >
> >
> > ------------------------------------------------------------------
> > David Germán Canteros
> >
> >
> > 2011/12/22 Lenny Primak <lpri...@hope.nyc.ny.us>
> >
> >> Bet the syntax checker is a bit overzealous. Unconfirmed though.
> >> I think you should file an issue.
> >>
> >> On Dec 22, 2011, at 3:56 PM, David Canteros wrote:
> >>
> >>> Mmm I have a doubt.. .why tapestry consider that asterisk symbol (*) is
> >>> unsafe?? (that symbol is my problem now). The specification for URLs
> >> (RFC
> >>> 1738 <http://www.rfc-editor.org/rfc/rfc1738.txt>, Dec. '94) says that
> >>> asterisk could be used unencoded...
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> >> For additional commands, e-mail: users-h...@tapestry.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
