searxng/searx/webapp.py, branch custom

[mod] defaults: GET method and ddg autocomplete

2026-08-12T11:05:02Z

[fix] autocompleter: suggestions contain HTML escape codes

2026-08-03T17:17:57Z

The results were previously HTML-escaped for some reason. That doesn't really make much sense because they never got unescaped anywhere. For example, `A&B` gets escaped to `A&B` and never unescaped, so the autocompletion frontend shows `A&B`, which isn't user-friendly at all. Also, it doesn't make sense to escape the full JSON instead of only escaping the suggestion texts individually because that makes it even more unclear.

[fix] autocomplete: drop POST method

2026-08-03T11:51:02Z

[fix] autocomplete suggestrelevance scores for chromium

2026-07-15T15:45:25Z

[chore] complete and normalize the attributes of engine objects (#6258)

2026-06-15T08:52:00Z

Drop outdated engine attributes: supported_languages, language_aliases Complete, normalize and document the type definitions for the engine-module and engine-class. For the ``engine.about`` section of the configuration, a type check is performed based on structure ``searx.enginelib.EngineAbout``. The property ``engine.about.language`` no longer exists; existing values have been migrated to ``engine.language``. Signed-off-by: Markus Heiser

[fix] sqlitedb: create DB Schema (DDL) during app initialization (hardening) (#6187)

2026-06-10T13:48:49Z

The initialization of the DB schema ("base schema") has so far been done on demand, which causes race conditions with competing threads and processes. The DDL statements for creating the "base schema" are now executed as part of the initialization of the app. Further improvements were made to harden the database applications: - Wikidata & Radio-Browser engine perform their initialization only once (so far the initialization was carried out in each thread/process). - If multiple processes try to set DB's WAL mode when opening the DB at the same time, this usually leads to another race condition, which is now also caught. Related: - https://github.com/searxng/searxng/issues/6181#issuecomment-4586705 Closes: #6181 Signed-off-by: Markus Heiser

[mod] typification of the preference settings

2026-05-30T14:43:50Z

no functional change / except the missing online doc which is now available:: $ make docs.live $ xdg-open "http://127.0.0.1:8000/admin/settings/settings_preferences.html" Signed-off-by: Markus Heiser

[unbload] drop meaningless field ``number_of_results_xpath`` from results (#6130)

2026-05-25T10:43:02Z

In the result-list, the ``number_of_results`` indicate the number of hits in the Index, they do not indicate how many results are in the answer. In the past, search engines such as google or ddg had an indication on the first page of a search term of how many hits there were for this term in total in their index. This info was added up in SearXNG and delivered under ``number_of_results``. Nowadays the search engines no longer indicate how many hits there are in the index and so this field in SearXNG is also superfluous. - https://github.com/searxng/searxng/issues/2457#issuecomment-2566181574 - https://github.com/searxng/searxng/issues/2987 - https://github.com/searxng/searxng/issues/5034 Signed-off-by: Markus Heiser

[fix] preferences: opening preferences page is very slow (multiple seconds on bad hardware) (#6090)

2026-05-21T19:15:09Z

I've been profiling the `/preferences` endpoint using werkzeug's `ProfilerMiddleware` (i.e. just do `app.wsgi_app = ProfilerMiddleware(app.wsgi_app)`) and look at the outputs in the terminal when doing `make run`. It turns out that 95%+ of the time spent were inside babel's Locale parsing (> 700ms on my machine). That's because, when opening the settings, we loaded the full engine traits of each engine and checked if it matches the user-defined search language. As we have 250+ engines, and babel is very slow when parsing Locale's, this took a very long time. By removing this feature that shows whether the selected search language is supported by the engine, the load time went down from 800ms to 50ms on my machine (which is still very slow, but well, that's future work on optimizing).

[mod] add manifest.json template and route (#5859)

2026-03-24T19:21:27Z

URLs, name and colors are automatically rendered into manifest.json. Furthermore user preference of theme (light, dark, black) and theme colors are respected. Theme colors can be set in settings.yml