| Age | Commit message (Collapse) | Author |
|---|
|
Bumps [jinja2](https://github.com/pallets/jinja) from 2.11.2 to 2.11.3.
- [Release notes](https://github.com/pallets/jinja/releases)
- [Changelog](https://github.com/pallets/jinja/blob/master/CHANGES.rst)
- [Commits](https://github.com/pallets/jinja/compare/2.11.2...2.11.3)
Signed-off-by: dependabot[bot] <support@github.com>
|
|
searx/dependabot/pip/master/nose2-coverage_plugin--0.10.0
|
|
Bumps [nose2[coverage_plugin]](https://github.com/nose-devs/nose2) from 0.9.2 to 0.10.0.
- [Release notes](https://github.com/nose-devs/nose2/releases)
- [Changelog](https://github.com/nose-devs/nose2/blob/master/docs/changelog.rst)
- [Commits](https://github.com/nose-devs/nose2/compare/0.9.2...0.10.0)
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
Only pip packages and ignore pygments, related to https://github.com/searx/searx/pull/2206
|
|
update yggtorrent url + add it back
|
|
Improve peertube searching
|
|
|
|
At the moment videos without a description are not shown - setting
default content to "" fixes this.
Another current bug is that thumbnails are not displayed. This is caused
by a double slash in the url. For this every trailing slash is now
stripped (for backwards compatibility) and the API response is correctly
parsed.
|
|
|
|
[remove] yandex engine
|
|
|
|
give the weekend to review the PR
|
|
[fix] duckduckgo engine: "!ddg !g" do not redirect to google
|
|
* searx understand "!ddg !g time" as : send "!g time" to DDG
* !g a DDG bang for Google: DDG return a HTTP redirect to Google
This commit adds a the allows_redirect param not to follow HTTP redirect.
The DDG engine returns a empty result as before without HTTP redirect.
|
|
[mod] json_engine: add content_html_to_text and title_html_to_text
|
|
[upd] wikipedia engine: return an empty result on query with illegal characters
|
|
[fix] fix seznam engine
|
|
Fix duckduckgo
|
|
Fix: activate raise_for_error by default
|
|
[enh] add engine MediathekViewWeb (API)
|
|
|
|
no paging support
|
|
on some queries (like an IT error message), wikipedia returns an HTTP error 400.
this commit returns an empty result instead of showing an error to the user.
|
|
Some JSON API returns HTML in either in the HTML or the content.
This commit adds two new parameters to the json_engine:
content_html_to_text and title_html_to_text, False by default.
If True, then the searx.utils.html_to_text removes the HTML tags.
Update crossref, openairedatasets and openairepublications engines
|
|
[Engine] Add Library of Congress engine
|
|
[fix] fix apk_mirror engine
|
|
[upd] remove google_play_music engine
|
|
After the main request, send a second to https://duckduckgo.com/t/sl_h
See https://github.com/searx/searx/issues/2259
|
|
HTTPAdapter
The duckduckgo engine requires an additional request after the results have been sent.
This commit makes sure that the second request uses the same HTTPAdapter
= the same IP address, and the same proxy.
|
|
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
|
|
|
|
Google Play Music has been replaced by Youtube music.
|
|
Fix commit d703119d3a313a406482b121ee94c6afee3bc307 :
Some engines need to parse the HTTP error but
raise_for_error is always set to False in the "request" function.
|
|
|
|
[fix] fix github action data-update.yml
|
|
|
|
Fix XPATHs in Naver engine
|
|
Add support for Chinese variants in Wikipedia
|
|
Ignore double-quotes when highlighting query parts
|
|
query parts
|
|
|
|
Closes #2540
|
|
[drop] metager - xpath engine won't work anymore
|
|
The new version of MetaGer needs to reload the reults (into a iframe) with a
unique tag (see HTML response below).
Implementing a dedicated metager-engine for searx makes no sense to me. The
great days of MetaGer seems to be ended. I remember the good old days this
project started in the 90's of the last century. But in the last few years it
becomes more and more crap. As the name suggested, MetaGer was made for
germans in the first place. They have added a english and spain translation but
the i18n is very poor compared to what searx offers.
It's a pity, lets drop MetaGer.
This is the first response, the id (b82679980656899ba5a17ffd02a56846) is unique
for each query:
$ curl "https://metager.org/meta/meta.ger3?eingabe=foo&submit-query=&focus=web"
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<link rel="stylesheet" href="/index.css?id=b82679980656899ba5a17ffd02a56846">
<script src="/index.js?id=b82679980656899ba5a17ffd02a56846"></script>
<title>foo - MetaGer</title>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
</head>
<body>
<iframe id="mg-framed" src="https://metager.org/meta/meta.ger3?eingabe=foo&submit-query=&focus=web&mgv=b82679980656899ba5a17ffd02a56846" autofocus="true" onload="this.contentWindow.focus();"></iframe>
</body>
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
|
|
[feat] recoll: add support for paging
|
|
|
|
[fix] Get correct locale with country from browser
|
|
Some of our interface locales include uppercase country codes,
which are separated by `_` instead of the more common `-`.
Also, a browser's `Accept-Language` header could be in lowercase.
This commit attempts to normalize those cases so a browser's
language+country codes can better match with our locales.
This solution assumes that our UI locales have nothing more than
language and optionally country. If we ever add a script specific
locale like `zh-Hant-TW` this would have to change to accomodate
that, but the idea would be pretty much the same as this fix.
|
|
[mod] CI: minor changes
|
