Sec-WebSocket-Protocol header is private[http]
Open
1 - triaged
help wanted
- Dominant language
- Scala
- Stars
- 1.4k
- Forks
- 584
- Avg merge
- 14h 33m
- Merged PRs (30d)
- 24
Description
**Issue by [analytically](https://github.com/analytically)**
_Tuesday Dec 22, 2015 at 11:06 GMT_
_Originally opened as https://github.com/akka/akka/issues/19258_
---
Overriding the default RejectionHandler is tricky for UnsupportedWebsocketSubprotocolRejection because Sec-WebSocket-Protocol is private.
Contributor guide
Research direction
Start by tracing UnsupportedWebsocketSubprotocolRejection and the Sec-WebSocket-Protocol header visibility in the HTTP and WebSocket handling code. Done means a custom RejectionHandler can handle this rejection while accessing the Sec-WebSocket-Protocol header.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100