Using relative links to openapi.json urls #24
MHugonKaliop
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
Hmm, not sure if this will be trivial but would love to review a PR for this! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using open-webui on a server behind a nginx proxy for https support.
After installing mcpo server, I was unable to make it work within open-webui because mcp server is exposed through http on port 8000 (default behaviour), resulting in various warnings and triggers in the browser...
So i've updated my nginx configuration in order to create a route for mcpo. My rule is simple, https://myserver/mcp redirects internally to http://myserver:8000 (I rewrite the url and removes the "mcp" part for mcpo.
This way, I was able to configure it, but my issue is that when trying to access https://myserver/mcp/xxx/docs, I've got an error due to the url sent back for openapi.json, which is https://myserver/xxx/openapi.json.
Is it possible to use relative link ? This way I'll receive https://myserver/mcp/xxx/openapi.json, and it will work.
Or maybe we could configure this prefix directly in mcpo, with somethink like :
mcpo --host 0.0.0.0 --port 8000 --url_path mcp ....
Beta Was this translation helpful? Give feedback.
All reactions