unsupported permessage-deflate parameter: "client_max_window_bits=15" from client
Open
- Dominant language
- Go
- Stars
- 5.5k
- Forks
- 372
- PR merge metrics
- No merged PRs in 30d
Description
If a websocket server reply with extension `permessage-deflate; client_max_window_bits=15` an error happens:
```
unsupported permessage-deflate parameter: "client_max_window_bits=15"
```
at
https://github.com/nhooyr/websocket/blob/bd07a64be6809ef46b76fff5ef7263ef7641980f/dial.go#L268-L300
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in dial.go around lines 268-300, where the server's permessage-deflate extension parameters are parsed. Reproduce the handshake with client_max_window_bits=15 and trace why that parameter is rejected; done means the valid server reply no longer produces the unsupported-parameter error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100