Lve Lvee
Lve Lvee
@i008 just copying the params from http request to websocket request... I'm still working through the source code.
@abidlabs I'd like to add some flag (in the URL) for Gradio to interact with other applications (e.g., one-time authentication/automatically fill out forms, etc.). In my business, I want to...
@abidlabs copy params from html to websocket would be better. We should only change here and related logics. https://github.com/gradio-app/gradio/blob/11bb732f5d12284aad1a139fd3891bd01ff1167d/ui/packages/client/src/client.ts#L260 This solution (https://huggingface.co/spaces/radames/gradio-url-params/blob/main/app.py) is too tricky, it requires additional javascript.
Hi @abidlabs Thanks for your explanation. I see. It's reasonable if our user only running **a** gradio instance. But if someone would like implement some middleware mechanism for **multiple** instances.
@abidlabs it's may **not** be a common concern. But for example, if someone would like to mount multiple Gradio instances onto a FastAPI site and add authentication or statistical middleware...
Actually, this question has nothing to do with nginx, any gateway can be used instead of nginx. Assuming we forward the request to gradio (address http://gradio) through the gateway (address...
A simpler example, if we set up a CDN for the gradio app, gradio will access /api/predict from the CDN instead of localhost. @abidlabs https://github.com/gradio-app/gradio/blob/f34120c0777abd4f2053179a6d0e0ad15c7b1fb3/gradio/routes.py#L477-L478 https://github.com/gradio-app/gradio/blob/eac49196a792563965bcddd8c3f9df28ba0c84a1/gradio/queueing.py#L319-L326