xtenzQ commented on PR #1829: URL: https://github.com/apache/solr/pull/1829#issuecomment-1681600877
@janhoy I've begun to question whether my current solution is more of a workaround rather than an actual resolution that eliminates the problem. To be honest, there are certain aspects that I find problematic. The situation involves managed resources within the URI, leading us to decode the entire URI due to its path nature. This becomes an issue when special characters like +, %, :, or / are present in synonyms/stopwords, as they become integrated into the path. While I haven't encountered clients in my work using `+` or `%`, they have certainly used `/` for things like abbreviations such as `AC/DC`. While my current solution solves this problem, it admittedly appears inelegant from my perspective and looks like a workaround. Here are a couple of potential solutions: 1. Decode only the portion of the URI that contains the synonym/stopword. However, this approach raises doubts, especially if the user submits a UTF-8 encoded request to the managed resource. Since I don't have much experience with REST, I'd appreciate input from the RestManager contributors on this matter. 2. Consider altering the way we handle the deletion of synonyms/stopwords. For instance, we could opt for using a PUT request instead of DELETE and embed the synonym/stopword within the request body. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
