HTTP_X_SCRIPT_NAME not removed from PATH_INFO

[drwilly]

I just migrated from radicale 1 to 2. My setup is nginx -> uwsgi -> radicale.
I used to rely on the base_prefix in radicale's config to get the SCRIPT_NAME and PATH_INFO parameters right which apparently is no longer possible.
My understanding of the parameter HTTP_X_SCRIPT_NAME is that it should overwrite SCRIPT_NAME and be stripped off of PATH_INFO. So if HTTP_X_SCRIPT_NAME = /radicale and PATH_INFO = /radicale/myuser/ then the latter should be rewritten to /myuser/.
However that does not seem to be the case: https://github.com/Kozea/Radicale/blob/master/radicale/__init__.py#L404

[Unrud]

This is the expected behaviour (see https://www.python.org/dev/peps/pep-0333/).
My suspicion is that nginx is not configured correctly: http://radicale.org/proxy/
The trailing slash causes nginx to strip /radicale from the path.

[drwilly]

Sorry it took me a while. Regardless ...
I am unsure how to translate the reverse-proxy configuration to my wsgi setup.
My working config looks as follows:

                location ~ ^/radicale(/.*|$) {
                        include                 uwsgi_params;
                        uwsgi_param SCRIPT_NAME /radicale;
                        uwsgi_param PATH_INFO   $1;
                        uwsgi_param REMOTE_USER $remote_user;
                        uwsgi_pass              unix:/run/uwsgi/radicale.socket;

                        auth_basic              "Restricted";
                        auth_basic_user_file    radicale.passwd;
                }

However as you can see it requires some url-matching and parameter-fiddling.
A plain location /radicale/ without explicitly setting PATH_INFO does not work.

[pbiering]

@chripo : is this still an issue with Radicale major version 3? If not, please close.

[mazhe]

I was just reviewing my own radicale configuration for refresh and can confirm this is still an issue (tested with radicale 3.1.18, will update soon to 3.2.x and nginx 1.24.0)

[pbiering]

I've did a major review of the "apache" reverse proxy config example (supporting 4 different flavors) and stored a template in the repository now: https://github.com/Kozea/Radicale/blob/master/contrib/apache/radicale.conf

Can you please align your "nginx" configuration and check whether the issue disappears then?

[pbiering]

there are now also small nginx config examples in repo https://github.com/Kozea/Radicale/tree/master/contrib/nginx - please validate and reopen if there is still an issue