summaryrefslogtreecommitdiff
path: root/tests/unit/settings
AgeCommit message (Collapse)Author
2024-01-31[mod] remove X-XSS-Protection headersMarkus Heiser
Deprecated header not used by browsers nowadays[1]: """In modern browsers, X-XSS-Protection has been deprecated in favor of the Content-Security-Policy to disable the use of inline JavaScript. Its use can introduce XSS vulnerabilities in otherwise safe websites. This should not be used unless you need to support older web browsers that don’t yet support CSP. It is thus recommended to set the header as X-XSS-Protection: 0."""[2] [1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection [2] https://infosec.mozilla.org/guidelines/web_security#x-xss-protection Closes: https://github.com/searxng/searxng/issues/3171 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2023-08-09[fix] make flask_babel.gettext() work in engine modules (L10n & threads)Markus Heiser
incident: flask_babel.gettext() does not work in the engine modules. cause: the request() and response() functions of the engine modules run in the processor, whose search() method runs in a thread and in the threads the context of the Flask app does not exist. The context of the Flask app is needed by the gettext() function for the L10n. Solution: copy context of the Flask app into the threads. [1] special case: We cannot equip the search() method of the processors with the decorator [1], because the decorator requires a context (Flask app) that does not yet exist at the time of the initialization of the processors (the initialization of the processors is part of the initialization of the Flask app). [1] https://flask.palletsprojects.com/en/2.3.x/api/#flask.copy_current_request_context Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2022-02-20[fix] changeover of the unit tests to the simple themeMarkus Heiser
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2021-07-25[mod] use tests/unit/settings/test_settings.yml in unit testsMarkus Heiser
In unit tests settings from searx/settings.yml and the user settings from: unit/settings/test_settings.yml are used. In the latter, settings can be activated that are needed in the unit test but should not activated by default in production. Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2021-06-05[yamllint] tests/unit/settings/user_settings_remove2.ymlMarkus Heiser
Fixed messages reported by:: make test.yamllint Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2021-06-05[yamllint] tests/unit/settings/user_settings_remove.ymlMarkus Heiser
Fixed messages reported by:: make test.yamllint Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2021-06-05[yamllint] tests/unit/settings/user_settings_simple.ymlMarkus Heiser
Fixed messages reported by:: make test.yamllint Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2021-06-05[yamllint] tests/unit/settings/user_settings_keep_only.ymlMarkus Heiser
Fixed messages reported by:: make test.yamllint Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2021-06-05[yamllint] tests/unit/settings/user_settings.ymlMarkus Heiser
Fixed messages reported by:: make test.yamllint Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2021-06-05[yamllint] tests/unit/settings/syntaxerror_settings.ymlMarkus Heiser
Fixed messages reported by:: make test.yamllint Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2020-12-03[fix] settings_loader: don't crash when a key exists only in the user settingsAlexandre Flament
typical use case: result_proxy can be defined in the user settings, but are not defined the default settings.yml
2020-11-27[enh] settings.yml: add use_default_settings option (2nd version)Alexandre Flament