Kong: Websocket Upgrade header missing after upgrade to 1.2.0

Created on 12 Jun 2019  路  2Comments  路  Source: Kong/kong

Summary

When publishing a an application that uses web sockets (via deepstream.io 3.2.4) after upgrading kong 1.1.2 to 1.20 the Upgrade response header is not passed to the client meaning a websocket connection fails to be established.

Steps To Reproduce

  1. Deploy websocket application (that uses websocket upgrade protocol) through kong 1.1.2
  2. Test that it works and if necessary capture http request logs using browser developer tools
  3. Follow the standard kong upgrade process to 1.2.0 with identical service and route configuration
  4. Test the same after the upgrade and note websockets will not be connected.

Additional Details & Logs

  • Kong version 1.2.0

Network logs

tasbug
Source
picture davebown
👍1

Most helpful comment

@subnetmarco now it is covered with PR #4719.

picture bungle on 12 Jun 2019
👍2

All 2 comments

@bungle this should also be covered in our integration tests

subnetmarco picture subnetmarco on 12 Jun 2019

@subnetmarco now it is covered with PR #4719.

bungle picture bungle on 12 Jun 2019
👍2
Was this page helpful?
0 / 5 - 0 ratings

Related issues

hbagdi picture hbagdi  路  3Comments
kwahome picture kwahome  路  3Comments
luka1983 picture luka1983  路  4Comments
hbagdi picture hbagdi  路  3Comments
vikaskmr1008 picture vikaskmr1008  路  3Comments