You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because I'm new to FastAPI, I recently realized that app's root_path (configured as APP_ROOT_PATH) is automatically prepended to mounted routes, such as /static or /mcp
As a result of this behavior, I had to configure my reverse proxy so that it strips the common prefix path (/{proxy}) for regular requests, while keeping the full path for mounted routes such as /{proxy}/static
Fortunately, it works well for now, but I wonder if this behavior is actually intended because It seems a bit complicated and counter-intuitive.
Let me know if I'm misusing mcp-context-forge or there is a better approach.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team,
Because I'm new to FastAPI, I recently realized that app's root_path (configured as APP_ROOT_PATH) is automatically prepended to mounted routes, such as
/staticor/mcpAs a result of this behavior, I had to configure my reverse proxy so that it strips the common prefix path (
/{proxy}) for regular requests, while keeping the full path for mounted routes such as/{proxy}/staticHere's my kong gateway config:
Fortunately, it works well for now, but I wonder if this behavior is actually intended because It seems a bit complicated and counter-intuitive.
Let me know if I'm misusing mcp-context-forge or there is a better approach.
Thanks for your time!
Beta Was this translation helpful? Give feedback.
All reactions