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. |
||
|---|---|---|
| .. | ||
| baidu.go | ||
| bing.go | ||
| duckduckgo.go | ||
| google.go | ||
| ollama.go | ||
| proxy.go | ||
| proxy_test.go | ||
| registry.go | ||
| searxng.go | ||
| searxng_test.go | ||
| tavily.go | ||