|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 1596 | minor | always | 02-01-07 07:57 | 05-25-07 18:07 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.2 | ||
|
|
|||||
| 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. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||