I've spotted behaviour that looks wierd: [uwsgi] master = true no-orphans = true http = :8080 wsgi-file = primary.py
plugins = router_basicauth route = ^/a basicauth:basic realm,foo:bar route = ^/b basicauth:basic realm2,foo:bar Correct login and password works as expected: lukasz.mierzwa@sudoku-admin:~/uwsgi$ curl -I -u foo:bar localhost:8080/a HTTP/1.1 200 OK Content-Type: text/plain lukasz.mierzwa@sudoku-admin:~/uwsgi$ curl -I -u foo:bar localhost:8080/b HTTP/1.1 200 OK Content-Type: text/plain Bit if I use invalid password first route doesn't throw 401, but second does: lukasz.mierzwa@sudoku-admin:~/uwsgi$ curl -I -u foo:barx localhost:8080/a HTTP/1.1 200 OK Content-Type: text/plain lukasz.mierzwa@sudoku-admin:~/uwsgi$ curl -I -u foo:barx localhost:8080/b HTTP/1.1 401 Authorization Required WWW-Authenticate: Basic realm="basic realm2" I should get 401 on both (?) -- Łukasz Mierzwa
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
