Update scrapix configuration file misc/config_examples/docusaurus-docsearch.json of meilisearch/scrapix to include a custom user-agent. "user_agents": ["foo"]
Observe the log output of meilisearch. docker logs -f meilisearch
Expected behavior
The HTTP "User-Agent" header from Caddy's log should be something similar to what the docs mentioned:
user_agents
An array of user agents that are append at the end of the current user agents.
In this case, if your user_agents value is ['My Thing (vx.x.x)'] the final user_agent becomes
Meilisearch JS (vx.x.x); Meilisearch Crawler (vx.x.x); My Thing (vx.x.x)
The HTTP "User-Agent" header from meilisearch's log should be something similar to the above mentioned value.
Steps to reproduce
misc/config_examples/docusaurus-docsearch.json
of meilisearch/scrapix to include a custom user-agent."user_agents": ["foo"]
yarn playground:docsearch
from meilisearch/scrapix.docker logs -f meilisearch
Expected behavior
The HTTP
"User-Agent"
header from Caddy's log should be something similar to what the docs mentioned:The HTTP
"User-Agent"
header from meilisearch's log should be something similar to the above mentioned value.Actual behavior
Caddy's log returns
node
as HTTP User-Agent.meilisearch's log returns
node
as HTTP User-Agent.