Will Sargent

There are a couple of posts that talk about parsing URIs: * http://blog.palominolabs.com/2013/10/03/creating-urls-correctly-and-safely/index.html * https://www.talisman.org/~erlkonig/misc/lunatech%5ewhat-every-webdev-must-know-about-url-encoding/ There are external libraries that will augment the functionality of WS: [galimatias](http://galimatias.mola.io/) validates URLs, and...

Note that play-ws-standalone is a pure interface-only API, so whatever is under the hood in play-mockws should work fine. There's always going to be extra dependencies in any implementation.

@fehmicansaglam that is entirely up to @f100ded / @tartakynov

Okay! Brought it up for discussion at https://discuss.lightbend.com/t/adding-mock-to-play-ws-standalone/1227 -- the advantage is it would be visible in the documentation, downside is that it would have to be published on the...

Also see https://github.com/xdotai/play-json-extensions

We can do the same thing we do on the client side: ```scala import play.api.mvc._ import play.api.libs.streams._ class Controller1 @Inject() (implicit system: ActorSystem, materializer: Materializer) { def socket = WebSocket.accept[String,...

Also see the Gigahorse support https://github.com/eed3si9n/gigahorse/blob/0.3.x/asynchttpclient/src/main/scala/gigahorse/support/asynchttpclient/WebSocketListener.scala and https://github.com/eed3si9n/gigahorse/commit/4ef7aaa3f8f39304227148b41413f6b0fdd22059

@AndrewZurn the workaround is to use play-ahc-ws (that is, the WS library with Play extensions).

Good catch.

@Malax within the next couple of weeks -- however, do note that due to the way that the standalone client works, it's fairly easy to create your own custom body...