[ 
https://issues.apache.org/jira/browse/SOLR-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074952#comment-14074952
 ] 

Hoss Man commented on SOLR-6163:
--------------------------------

A quick glance at timo's patch and the javadocs for the assocaited restlet 
classes seems to suggest that this is correct general course of action...

http://restlet.com/learn/javadocs/2.1/jse/api/org/restlet/data/Reference.html#getPath%28%29
"Note that no URI decoding is done by this method. "

A cleaner fix is probably to use this alternative restlet method that an decode 
for us ...

http://restlet.com/learn/javadocs/2.1/jse/api/org/restlet/data/Reference.html#getPath%28boolean%29

There are lots of similar "Note that no URI decoding is done by this method." 
and "Returns the optionnally decoded ______" combinations in the Request class 
-- we should probably audit all of our usages of this class.


> special chars and ManagedSynonymFilterFactory
> ---------------------------------------------
>
>                 Key: SOLR-6163
>                 URL: https://issues.apache.org/jira/browse/SOLR-6163
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.8
>            Reporter: Wim Kumpen
>
> Hey,
> I was playing with the ManagedSynonymFilterFactory to create a synonym list 
> with the API. But I have difficulties when my keys contains special 
> characters (or spaces) to delete them...
> I added a key ééé that matches with some other words. It's saved in the 
> synonym file as ééé.
> When I try to delete it, I do:
> curl -X DELETE 
> "http://localhost/solr/mycore/schema/analysis/synonyms/english/ééé";
> error message: %C3%A9%C3%A9%C3%A9%C2%B5 not found in 
> /schema/analysis/synonyms/english
> A wild guess from me is that %C3%A9 isn't decoded back to ééé. And that's why 
> he can't find the keyword?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to