uwsgi routes / to the first mounted app, even though path doesn't match route #1935

reece · 2018-11-29T05:25:22Z

uwsgi 2.0.17.1, Python 3.6

Problem

uwsgi routes / to the first mounted app, even though / does not match the route mount path.

Steps to reproduce:

snafu$ python3.6 -mvenv venv/3.6
snafu$ . venv/3.6/bin/activate
(3.6) snafu$ pip install -U pip setuptools
(3.6) snafu$ pip install uwsgi flask

(3.6) snafu$ head bug1.py uwsgi.ini
==> bug1.py <==
from flask import Flask
app = Flask(__name__)

@app.route("/")
def hello():
    return "You may call me " + __name__ + "\n"

==> uwsgi.ini <==
[uwsgi]
mount = /bug1=bug1.py
callable = app
http-socket = :9090

Start with uwsgi --ini=uwsgi.ini. In another window:

(3.6) snafu$ for url in http://localhost:9090/{bug1/,bug/,}; do (set -x; curl $url); done
+ curl http://localhost:9090/bug1/
You may call me uwsgi_file_bug1
+ curl http://localhost:9090/bug/
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>404 Not Found</title>
<h1>Not Found</h1>
<p>The requested URL was not found on the server.  If you entered the URL manually please check your spelling and try again.</p>
+ curl http://localhost:9090/
You may call me uwsgi_file_bug1

Logs in first window:

[pid: 19540|app: 0|req: 1/1] 127.0.0.1 () {24 vars in 242 bytes} [Wed Nov 28 21:21:34 2018] GET /bug1/ => generated 32 bytes in 0 msecs (HTTP/1.1 200) 2 headers in 79 bytes (1 switches on core 0)
[pid: 19540|app: 0|req: 2/2] 127.0.0.1 () {24 vars in 240 bytes} [Wed Nov 28 21:21:34 2018] GET /bug/ => generated 233 bytes in 8 msecs (HTTP/1.1 404) 2 headers in 72 bytes (1 switches on core 0)
[pid: 19540|app: 0|req: 3/3] 127.0.0.1 () {22 vars in 232 bytes} [Wed Nov 28 21:21:34 2018] GET / => generated 32 bytes in 0 msecs (HTTP/1.1 200) 2 headers in 79 bytes (1 switches on core 0)

The text was updated successfully, but these errors were encountered:

eclectronical · 2019-10-08T01:48:02Z

It's a shame you didn't get any response from the maintainers after all this time, but the answer is to use --no-default-app (or no-default-app = 1 in an .ini file). This is documented, but not very well.

Unfortunately this still doesn't work quite right as it returns a 500 instead of a 404 for requests that don't hit any app.

ApproximateIdentity · 2021-09-10T13:57:50Z

Thank you for the information @eclectronical

Unfortunately this still doesn't work quite right as it returns a 500 instead of a 404 for requests that don't hit any app.

Does anyone here know if this is the intended behaviour? In other words, would the fact that 500 in this instance be considered a bug by the uwsgi team? In that case a fix would be appropriate.

Currently an error code of 500 is returned when no app is found for a route, but this changes it to a 404 which seems more appropriate. See this issue for more context: unbit#1935

ApproximateIdentity mentioned this issue Sep 10, 2021

Change errror code to 404 if no app is found #2343

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

uwsgi routes / to the first mounted app, even though path doesn't match route #1935

uwsgi routes / to the first mounted app, even though path doesn't match route #1935

reece commented Nov 29, 2018

eclectronical commented Oct 8, 2019 •

edited

Loading

ApproximateIdentity commented Sep 10, 2021

uwsgi routes / to the first mounted app, even though path doesn't match route #1935

uwsgi routes / to the first mounted app, even though path doesn't match route #1935

Comments

reece commented Nov 29, 2018

Problem

Steps to reproduce:

eclectronical commented Oct 8, 2019 • edited Loading

ApproximateIdentity commented Sep 10, 2021

eclectronical commented Oct 8, 2019 •

edited

Loading