mirror of
https://github.com/open-webui/open-webui.git
synced 2026-09-27 08:28:02 -05:00
Classic298
420b4a2797
A link whose host refuses the connection, such as a closed port, still came back from POST /api/v1/retrieval/process/web as "Error querying knowledge base", so the caller was told the knowledge base failed when the link was the problem. The web loaders log a failed fetch and return no documents. That empty result then failed while being saved to the vector store, and the save error was the one reported. process_web now answers with the existing "Could not read content from <url>" 400 as soon as the loader returns no documents, the same message a link refused by the fetch filter already gets. The check sits in the endpoint so web search and the other users of the loaders keep their current behaviour. With process=false or embedding bypassed, an unreachable link now gets the same 400 where it used to return 200 with empty content. Fixes #31347