Hello list, We've been using Stripes for sevaral months in our projects and so far it's been great. However, we stumbled upon a problem I'd like to discuss.
Tomcat by default is configured to handle ISO-8859-1 encoded URLs, that is, when a non-ASCII character is encoded with %nn in a URL, that nn is assumed to be the code for a character in the ISO-8859-1 charset. It is possible to change this default in Tomcat on a per-connector basis, but there are cases when our application runs on a Tomcat installation that we have no control over. However, the Stripes UrlBuilder (or better the StringUtil class it uses) always encodes/decodes URLs in UTF-8. This breaks URLs with non-ASCII characters, as well as RedirectResolution and everything else that uses UrlBuilder, when used on a default Tomcat installation, or one which has been configured to encode URLs in some encoding different from UTF-8. And it's pretty much impossible to override from user code. Since in our applications we generally try not to store anything in session, we tend to pass certain user-provided data around as GET parameters. We could manually encode that data to ASCII, but I think that if Stripes made the URL character encoding configurable, we could avoid some hassle. Has someone else encountered the same problem? Are we doing something wrong? Regards, Alessio ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
