Possible Accept Headers out of date for Several Engines (triage) #3476
Replies: 3 comments
-
Can you easily check 1) which engines are broken at the moment and 2) which engines would get fixed with the simple Accept Header addition? |
Beta Was this translation helpful? Give feedback.
-
Sadly I don't have a script. What I'm thinking of doing is adding a test(s), skipped by default (or only warn on failure and not fail the test suite), which one-by-one calls each engine with a query that should provide results to see if we can get at least one result. I would consider this an integration test, so I'll likely place it into a new folder named "integration" in the test path. This should greatly assist us now, and anyone in the future adding new engines. |
Beta Was this translation helpful? Give feedback.
-
@juusoohtonen I have a Draft PR that includes integration tests based on set of engines. Below is an image of a sample output of the integration tests. |
Beta Was this translation helpful? Give feedback.
-
This issue for Bing resulted in using an Accept Header that wasn't valid.
juusoohtonen mentioned that DDG is also not returning results. With this, I'll use this discussion for finding the impact of each engine that might be affected by this. Its a pretty simple fix, so shouldn't be too bad.
We should try to query each engine currently in Searx individually and see which ones are not returning results, and then see if a simple Accept Header update will fix it.
Beta Was this translation helpful? Give feedback.
All reactions