Port forwarding feature via subdomain/path

Is it possible to provide port forwarding feature that native VS Code provides?

The Coder web version of VS Code also provides this here: https://coder.com/docs/code-server/latest/guide#accessing-web-services-1

The above linked service does it by proxying all requests to <port>.somesubdomain.com to the application running on that port in the container. Another way it provides is <url_to_access_vscode_online>/proxy/<port>.

[aptalca]

fyi, we implemented that feature via an nginx trick in our SWAG reverse proxy. We simply use a named group in the server_name regex to capture the port as a var, and use that var in the proxy_pass directive: https://github.com/linuxserver/reverse-proxy-confs/blob/master/openvscode-server.subdomain.conf.sample#L74

[TiemenSch]

I think there are a couple of possible duplicate issues: #320 and to some extent #163

The mentioned workaround by @aptalca works using an additional prefix rather than a subpath. Could we get it to work with a subpath, too?

Something along the lines of:

server {
    listen 8888;
    listen [::]:8888;

    server_name example.com;

    location /code/ {
        proxy_set_header    X-Real-IP  $remote_addr;
        proxy_set_header    X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header    Host $http_host;
        proxy_redirect      off;
        rewrite             ^/code/(.*) /$1 break;
        proxy_pass          http://127.0.0.1:3000;
    }

    location /code {
        return 301 /code/;
    }
}

where we should get it running on example.com:8888/code. That doesn’t work though, but I’ve got no clue if this is at all possible with only an NGINX configuration.