Repository navigation
|
Hi folks, To secure it, I use Caddy as reverse proxy, handling certificates It is supposed to be protected with a password or Token, the config snipet of the Caddyfile looks like this: It is all containerized an working. I use it as my own meta search engine. However I want that picoclaw could use this search engine as well and I can't figure out how. That's the step missing: Any ideas? Best regards |
Replies: 1 comment 1 reply
|
There's no header or API key setting for SearXNG: the provider only has So let Caddy accept a Basic credential next to your Bearer one: with "searxng": {
"enabled": true,
"base_url": "https://picoclaw:<token>@search.example.com"
}(If the token contains characters like I tested the chain locally with Caddy 2.11.7 and a small Go program that builds the request exactly like picoclaw: with the Also check that |
There's no header or API key setting for SearXNG: the provider only has
base_url/max_results, and builds a plainGET {base_url}/search?q=…&format=json(pkg/tools/integration/web.go). But since it's Go'snet/http, you can put credentials in the URL: when the URL has auser:password@part, Go sends it as anAuthorization: Basic …header automatically.So let Caddy accept a Basic credential next to your Bearer one: