| Age | Commit message (Collapse) | Author |
|
Server Timing specification: https://www.w3.org/TR/server-timing/
In the browser Dev Tools, focus on the main request, there are the responses per engine in the Timing tab.
|
|
themes accordingly.
|
|
|
|
|
|
|
|
|
|
This reverts commit 4d1770398a6af8902e75c0bd885781584d39e796.
|
|
Add match_language function in utils to match any user given
language code with a list of engine's supported languages.
Also add language_aliases dict on each engine to translate
standard language codes into the custom codes used by the engine.
|
|
|
|
|
|
Remove 'all' option from search languages
|
|
|
|
|
|
|
|
curl 'http://127.0.0.1:8888/?q=xxxxxxxx&categories=general&format=json'
|
|
Closes #1047
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
an valid feed including an error.
|
|
The exact order is
* first from SEARX_SETTINGS_PATH,
* if not found then from searx code base,
* if not found then from /etc/searx/settings.yml
* if not found an exception stops searx loading
|
|
|
|
|
|
|
|
|
|
message is output in json and rss format.
|
|
common place for shared templates.
What has been moved into this template :
* opensearch*.xml is always the same whatever the themes.
* the text inside */about.html
|
|
|
|
|
|
supported_languages, time_range_support, timeout fields.
|
|
another framework easier.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
utils/fetch_languages.py gets languages supported by each engine and
generates engines_languages.json with each engine's supported language.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|