Provide a way to disable {searchTerms} escaping on a search engine basis
See original GitHub issueHi,
As per this comment, it seems that there is a use for *not* escaping {searchTerms}
with some search engines. An example of such an engine is the Wayback Machine, which will not support a network request such as https://web.archive.org/web/*/https%3A%2F%2Fgithub.com%2F
and really need https://web.archive.org/web/*/https://github.com/
in order to work.
Some use cases involve selecting text that happens to be a valid URL, or pasting a valid URL in SSS’s pop-up text field, in order to search for it.
The feature you seem to have in mind to answer this is to give the user a way to disable escaping, at least for {seachTerms}
, on a search engine basis. Maybe you were thinking of an UI option, like the current text encoding drop down menu, or maybe of new syntax, like {searchTerms(noEscape)}
, or maybe something else entirely.
Thanks for your time!
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
@ZIEXED Sorry if that was confusing. I should have been clearer, especially considering that URL encoding is a security feature. I didn’t expect many of my search engines not to use it, only the most unusual ones. For example I checked DeepL, it uses a POST request with JSON in which the user input is not escaped client-side. But SSS makes GET requests so it’s irrelevant, I can’t hide that I’m one of only a few people to request translations in this way, regardless of URL encoding being disabled or not. In that case, might as well keep it.
Even now I still haven’t found an engine other than the Wayback Machine where it makes sense to disable escaping. I don’t have that many though.
I see. 😃 Btw, spaces are sometimes encoded as
+
(ex.: Google), but%20
is the proper encoding.