Skip to content

Enable path component when connecting via WebSocket#1514

Merged
scottf merged 3 commits intonats-io:mainfrom
jbaeck:feature/ws-enable-path
Jan 12, 2026
Merged

Enable path component when connecting via WebSocket#1514
scottf merged 3 commits intonats-io:mainfrom
jbaeck:feature/ws-enable-path

Conversation

@jbaeck
Copy link

@jbaeck jbaeck commented Jan 9, 2026

When a WebSocket connection url is specfied via ws://HOST:IP/PATH the PATH will now be included when establishing the connection.

I need help implementing a Test as I have not found a way to define the path in the nats websocket configuration.

@scottf
Copy link
Contributor

scottf commented Jan 9, 2026

@jbaeck For the test, we would have to mock a proxy of some sort? For now, as long as all the websocket tests pass confirming nothing is broken, and you manually confirm via a comment that you have tested your new pathways, I can live with that.

@jbaeck
Copy link
Author

jbaeck commented Jan 9, 2026

@scottf - all manual tests against my environment worked as well as the existing Tests.
I am really happy that in the end it’s a small change !

Anything else I could look into ?

@scottf scottf merged commit 93b79d8 into nats-io:main Jan 12, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants