# WebSockets byte array response

**URL:** <https://community.gatling.io/t/websockets-byte-array-response/3825>\
**Category:** Gatling (Open-Source)\
**Created:** [July 15, 2017, 3:48pm UTC](https://community.gatling.io/t/websockets-byte-array-response/3825 "2017-07-15T15:48:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Connor\_Reid](https://avatars.discourse-cdn.com/v4/letter/c/5fc32e/32.png) [@Connor\_Reid](https://community.gatling.io/u/Connor_Reid)\
**Post date:** [July 15, 2017, 3:48pm UTC](https://community.gatling.io/t/websockets-byte-array-response/3825/1 "2017-07-15T15:48:44Z")

</div>

I am using Gatling to test a server which supports WebSockets. My issue is that the server sends a byte array in the WebSockets response and, after reading line 177 in WsActor.scala in the Gatling source, I can see that “byte message checks are currently not supported”. If I was to go about implementing support to save byte array WebSockets responses, how would I do so? Without understanding the internals of the Gatling WebSockets implementation, I wouldn’t know where to start.

Also, it would be great if the Gatling dev team would implement support for WebSockets byte message checks.

- Connor

---

<div class="post-metadata">

**Author:** ![Connor\_Reid](https://avatars.discourse-cdn.com/v4/letter/c/5fc32e/32.png) [@Connor\_Reid](https://community.gatling.io/u/Connor_Reid)\
**Post date:** [July 15, 2017, 3:51pm UTC](https://community.gatling.io/t/websockets-byte-array-response/3825/2 "2017-07-15T15:51:14Z")

</div>

Also I am using version 2.2.5.