Support for Dynamic WebSocket Path Routing (e.g. /{organization}/{chargepoint})

[dwlpra]

❔ What is your question?

Hi, thank you for this great library.
I’m building a multi-tenant CSMS using ocpp-go, and I need to support WebSocket URLs with dynamic routing patterns, like:
ws://localhost:8887/{organization_code}/{chargeBoxIdentity}

For example:
ws://localhost:8887/acme-corp/cs-01

In this setup:

• acme-corp is the tenant/organization code
• cs-01 is the ChargeBoxIdentity (endpoint)

Currently, the csms.Start(port, path) function accepts only a static path (e.g. /ws), and connections outside this path are not handled by the central system.

❓ Question:

Is there a way to override or extend the path handling logic to support dynamic paths like /{org}/{id}?

🔧 What I've tried:

I attempted to use http.HandleFunc("/", customHandler) and manually upgrade the connection, but it seems ocpp-go uses its own internal WebSocket handling via the ws package.

🧩 Ideal solution:

Expose a way to:

• Intercept or route based on the full URL path
• Extract custom routing parameters (org, id)
• Still pass the connection to central.NewCentralSystem() properly

Is this currently supported? If not, would you accept a contribution/PR that allows pluggable path handling or routing logic?

Thank you in advance!

Which OCPP version referring to?

• OCPP 1.6
• OCPP 2.0.1

Are you using any OCPP extensions?

• OCPP 1.6 Security
• OCPP 1.6 Plug and Charge

👀 Have you spent some time to check if this question has been asked before?

• I checked and didn't find a similar issue

[xBlaz3kx]

It would be helpful if you explained what do you aim to achieve with "dynamic routing" - is it authenticating charge points based to the provided tenant? There are a couple of ways to achieve that without any library modifications.

[qosmotec]

we are also using dynamic urls, we achieved that the following way:

	wsServer = ws.NewServer()
	wsServer.SetChargePointIdResolver(func(r *http.Request) (string, error) {
		url := r.URL
		code, chargeBoxIdentity := path.Split(url.Path)
		id := fmt.Sprintf("%s+%s", path.Base(code), chargeBoxIdentity)
		if len(code) == 0 || code == "/" { /* code not provided */
			id = chargeBoxIdentity
		}
		return id, nil
	})

In your code you might parse chargeBoxIdentity to get code/clientId

Is this what you are looking for?

[AndrewYEEE]

Maybe you can use nginx to implement path reorganization?

Nginx URL Input:
https://host/CSMS/CP

Nginx URL Output:
https://host/CSMS_CP

https://www.digitalocean.com/community/tutorials/nginx-rewrite-url-rules

==========================
Notice!! WebSocket needs to be set up as follows:

location /URL{
proxy_pass http://XXXXXX;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
}

[xBlaz3kx]

I agree with @AndrewYEEE; its simpler (and also scalable in the long run) to have a Gateway/proxy to do the routing for you.
You could also spin up server instances per tenant, ensuring enough resources for each tenant individually.