3 ms·
The problem is that the search query does not go in the URL in the Lite version. That really sucks. It makes it useless in the browser history as well. In fact,
by jolmg 7y ago
The problem is that the search query does not go in the URL in the Lite version. That really sucks. It makes it useless in the browser history as well. In fact, because all the URLs are the same on each query, they're not even added as separate entries in the history.
- dredmorbius 7y agoThey don't? Search term(s) are the URL parameter: ?q=<query> Which does show in my history AFAICT.
- jolmg 7y agoOn the regular version, not the lite. Here's my URL after searching for "asdf": https://duckduckgo.com/lite/ https://duckduckgo.com/lite/ In the search form, it uses POST instead of GET to perform the searches.
- Arnavion 7y agoEven if the search form uses POST, the server does read the parameter if it's specified in the querystring. That is, https://duckduckgo.com/lite/?q=asdf https://duckduckgo.com/lite/?q=asdf works, so adding it as a search engine with URL .../?q=%s should work as well.
- jolmg 7y agoThat's nice I guess. Still a shame the text input can't be used without forgoing the history.