The current URLEncoder exists because different servlet contains interpreted the spec differently, in terms of weather the contents of the URL are uudecoded before being exposed (via the HttpServetRequest) to the application.
On Tue, Mar 17, 2009 at 5:59 AM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > Hi! > > I would like to bring a JIRA to your attention: > https://issues.apache.org/jira/browse/TAP5-539. It deals with the > current URLEncoder. IMHO, it has two major problems: > > 1) It is not compatible with standard URL encoding > 2) It produces very ugly URLs for non-7-bit-ASCII characters, > something very annoying any language that has accented characters. > > There are some messages in the mailing list concerning this. > > Of course, I could implement this myself, but unfortunately I'm not > able to devote any time to Tapestry in the next weeks. :( > > -- > Thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
