feat: Stop using hard-coded params in searxng.py

[ReiSuzunami]

Check Existing Issues

• I have searched the existing issues and discussions.

Problem Description

I think the config of SearxNG should be open to users, like SafeSearch, Language, Time, Category and ImageProxy.

I have deployed my own SearxNG instance and I found my settings were overwritten by hard-coded query params inside backend/open_webui/retrieval/web/searxng.py:

    params = {
        "q": query,
        "format": "json",
        "pageno": 1,
        "safesearch": safesearch,
        "language": language,
        "time_range": time_range,
        "categories": categories,
        "theme": "simple",
        "image_proxy": 0,
    }

# Codes...

    response = requests.get(
        query_url,
        headers={
            "User-Agent": "Open WebUI (https://github.com/open-webui/open-webui) RAG Bot",
            "Accept": "text/html",
            "Accept-Encoding": "gzip, deflate",
            "Accept-Language": "en-US,en;q=0.5",
            "Connection": "keep-alive",
        },
        params=params,
    )

My Open-WebUI could not reach the Public Internet, so I must use ImageProxy with a custom PlayWright server to make Web Searching possible and current version of SearxNG plugin is keeping me from that.

It will be nice if anyone could fix this.

Desired Solution you'd like

Make the attributes in the params editable via ENV or on the Web Interface..

Alternatives Considered

No response

Additional Context

No response

[tth37]

I think this issue would be resolved if #12822 gets merged? Or do you think there's still a need for custom searxng parameter configuration?

[ReiSuzunami]

Well it did not change any hard-coded params when open-webui requests the searxng server...

I still have no option to turn on the image proxy

[tth37]

To enable the image proxy for searxng integration, is setting params['image_proxy']=True sufficient, or are other configuration parameters also required?

[ReiSuzunami]

To enable the image proxy for searxng integration, is setting params['image_proxy']=True sufficient, or are other configuration parameters also required?

But no method could be used if I don't edit the sourcecode and compile my own version. I'm using the official docker image so the modification would be quite complex.

[tth37]

But no method could be used if I don't edit the sourcecode and compile my own version. I'm using the official docker image so the modification would be quite complex.

I understand, just to confirm, would adding a new config option like SEARXNG_USE_IMAGE_PROXY=True/False be sufficient to enable the image proxy feature, or is any other configurations needed?

[ReiSuzunami]

But no method could be used if I don't edit the sourcecode and compile my own version. I'm using the official docker image so the modification would be quite complex.

I understand, just to confirm, would adding a new config option like SEARXNG_USE_IMAGE_PROXY=True/False be sufficient to enable the image proxy feature, or is any other configurations needed?

The best situation is every single param could be set by env.