[Solved] What will be the effect of this Nginx config when proxying to Flask? location /app { proxy_pass http://127.0.0.1:5000; } Client requests http://example.com/app/page. | Flask

Flask - Deployment

What will be the effect of this Nginx config when proxying to Flask?

location /app {
    proxy_pass http://127.0.0.1:5000;
}

Client requests http://example.com/app/page.

ARequest forwarded to http://127.0.0.1:5000/app/page

BRequest forwarded to http://127.0.0.1:5000/page

CRequest forwarded to http://127.0.0.1:5000/app

DRequest returns 403 Forbidden

Step-by-Step Solution

Solution:

Step 1: Understand proxy_pass without trailing slash
When proxy_pass URL has no trailing slash, Nginx appends the full request URI after the location prefix.
Step 2: Apply to example
Location is /app, proxy_pass is http://127.0.0.1:5000. So request /app/page is appended fully, forwarding to http://127.0.0.1:5000/page.
Final Answer:
Request forwarded to http://127.0.0.1:5000/page -> Option B
Quick Check:
No trailing slash means location prefix replaced with proxy_pass URI [OK]

Quick Trick: No trailing slash in proxy_pass means location prefix is replaced [OK]

Common Mistakes:

MISTAKES

Master "Deployment" in Flask

9 interactive learning modes - each teaches the same concept differently

More Flask Quizzes

What will be the effect of this Nginx config when proxying to Flask?