Page reload websocket connection doesn't use `pathPrefix`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 109
- Forks
- 20
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
We want to use the eleventy dev server behind a reverse proxy, utilising Nginx.
However, the websocket connection, to get notified of changes, always connects to ws://localhost and does not respect the pathPrefix. All other files are served from the pathPrefix path correctly.
What do you think about using the pathPrefix for ws connections as well?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the dev server's websocket connection setup and how pathPrefix is applied to other served files. Reproduce the connection through an Nginx reverse proxy, then verify that reload notifications connect and function under the configured pathPrefix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100