Web service tree configuration and path matching

[oberstet]

Here is how Nginx can be configured to reverse proxy to Jupyter:

        location / {
            proxy_pass http://jupyter;

            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header Host $host;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        }
     location ~* /(api/kernels/[^/]+/(channels|iopub|shell|stdin)|terminals/websocket)/? {
            proxy_pass http://jupyter;

            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header Host $host;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            # WebSocket support
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection $connection_upgrade;

       }

source: https://gist.github.com/cboettig/8643341bd3c93b62b5c2

---

this has a regex to exactly match what paths are to be reverse proxied with websocket:

/(api/kernels/[^/]+/(channels|iopub|shell|stdin)|terminals/websocket)/?

to replicate that, we need 2 things:

• more advanced pattern matching on URL paths of Web service configuration
• more advanced configuration file format for Web service trees (the internal management API already has that power .. only the config.json is lacking because it uses URL paths for dict keys, whereas that should also be just a list of Web services (like workers) OR at least use Web service configuration item IDs for dict keys instead of URL paths.

[ecorm]

To replicate nginx, you would also need to loosen path character restrictions. See #308