WeKnora/internal/infrastructure/web_search
wizardchen 5fb7e692e5 refactor(web-search): drop dead api_key path in SearXNG provider
The SearXNG provider forwarded `parameters.api_key` as
`Authorization: Bearer <key>` for reverse-proxy auth, but the frontend
never rendered the API key input for self-hosted providers
(`requires_api_key=false`), so the path was unreachable from the UI.

Rather than expose another UI knob for a niche reverse-proxy setup that
the project does not currently support, remove the Authorization header
branch and the `apiKey` field on `SearxngProvider`. Tenants who put
SearXNG behind an authenticating reverse proxy can still front it with
network-level auth (mTLS, IP allowlist) without changes here.

`WebSearchProviderParameters.APIKey` is generic and used by other
providers, so it stays.
2026-05-11 16:53:47 +08:00
..
baidu.go feat(web-search): add baidu web search provider support #907 2026-04-12 20:13:05 +08:00
bing.go feat: search engine adds proxy addresses and adds SSRF verification. 2026-04-17 16:38:02 +08:00
duckduckgo.go feat: search engine adds proxy addresses and adds SSRF verification. 2026-04-17 16:38:02 +08:00
google.go feat: search engine adds proxy addresses and adds SSRF verification. 2026-04-17 16:38:02 +08:00
ollama.go feat(web-search): add ollama web search provider support #907 2026-04-10 01:27:29 +08:00
proxy.go feat: search engine adds proxy addresses and adds SSRF verification. 2026-04-17 16:38:02 +08:00
proxy_test.go feat: search engine adds proxy addresses and adds SSRF verification. 2026-04-17 16:38:02 +08:00
registry.go feat(web-search): refactor web search provider 2026-03-31 20:22:34 +08:00
searxng.go refactor(web-search): drop dead api_key path in SearXNG provider 2026-05-11 16:53:47 +08:00
searxng_test.go feat(searxng): enhance SearXNG configuration and validation 2026-05-11 16:53:47 +08:00
tavily.go feat: search engine adds proxy addresses and adds SSRF verification. 2026-04-17 16:38:02 +08:00