# Web Socket Error on AmazonEchoControl binding every 65 seconds

**URL:** <https://community.openhab.org/t/web-socket-error-on-amazonechocontrol-binding-every-65-seconds/100581>\
**Category:** Bindings\
**Tags:** amazonechocontrol\
**Created:** [June 12, 2020, 7:46pm UTC](https://community.openhab.org/t/web-socket-error-on-amazonechocontrol-binding-every-65-seconds/100581 "2020-06-12T19:46:16Z")\
**Posts on this page:** 1\
**Showing post:** 191

<div class="post-metadata">

**Author:** ![J-N-K](https://community.openhab.org/user_avatar/community.openhab.org/j-n-k/32/19276_2.png) [@J-N-K](https://community.openhab.org/u/J-N-K)\
**Post date:** [June 15, 2020, 10:22pm UTC](https://community.openhab.org/t/web-socket-error-on-amazonechocontrol-binding-every-65-seconds/100581/191 "2020-06-15T22:22:14Z")

</div>

Setting jetty to DEBUG shows the requests. It’s a bit hard to see, because jetty is very chatty at DEBUG.

After I found that, I originally thought that amazon is blocking jetty as user-agent and tried to set the user-agent header to a more common Mozilla. To my surprise this resulted in two user-agent headers which is obviously wrong. I then had a closer look at the other headers and found the the binding adds headers that are later added by jetty. After I removed that, the connection succeeded.

I‘m not entirely sure if this should be considered a bug in jetty. If I pass a request to the client, IMO it should not add already existing headers.

---

_[View the full topic](https://community.openhab.org/t/web-socket-error-on-amazonechocontrol-binding-every-65-seconds/100581)._