akka/akka-http

Support for WebSocket Extensions

Open

#659 opened on Dec 15, 2016

View on GitHub
 (13 comments) (5 reactions) (0 assignees)Scala (1,311 stars) (598 forks)batch import
1 - triagedhelp wantednice-to-have (low-prio)t:coret:websocket

Description

Continuation of akka/akka#18709 We currently do not support websocket extensions (i.e. registering "an extension" in the server, or requesting one in the client).

Currently we see no strong need to provide this functionality. If you have a strong use case for it, please comment here

Contributor guide

Tech stack
scala
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
ScalaWebSocket protocolAkka HTTP internalsWebSocket extensions RFC 6455
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the current WebSocket implementation in akka http, particularly the handshake and frame processing. Review the referenced issue akka/akka#18709 for previous discussion. Understand the WebSocket extension negotiation as per RFC 6455 and define a minimal API for extension registration. Consider how to integrate with the existing WebSocket server and client code.