Anonymous | Login | Signup for a new account | 12-17-2024 08:27 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0001596 | [Resin] | minor | always | 02-01-07 07:57 | 05-25-07 18:07 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | |||||||
Summary | 0001596: utf-8 in query parameter | ||||||||
Description |
(rep by Yonik Seeley) I haven't been able to get resin to accept UTF-8 in the URL. Seems like resin isn't following RFC 3986: http://www.ietf.org/rfc/rfc3986.txt [^] Adding <url-character-encoding>UTF-8</url-character-encoding> To the <server> element in resin.conf did not change the behavior. The specific part of the RFC: the data should first be encoded as octets according to the UTF-8 character encoding [STD63]; then only those octets that do not correspond to characters in the unreserved set should be percent- encoded. For example, the character A would be represented as "A", the character LATIN CAPITAL LETTER A WITH GRAVE would be represented as "%C3%80" If you pass something like /solr/q=%C3%80 to resin (3.0.22), the servlet received two chars instead of one. |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |