Websockets and declarative syntax

Questions
#1

Hi there,

I have this particular kong.yml which declares some of my services and routes using cors, though there are a couple that are websockets, I have read the doc and get rid of some issues at this point I think all the ideas in my head are depleted, wondering if you can help me to pin point what could’ve done it wrong, please find attach my config and error:

KONG.yml

- connect_timeout: 60000
  host: notification-ms
  name: notification-ms
  path: /
  port: 8080
  protocol: http
  read_timeout: 60000
  retries: 5
  write_timeout: 60000
  routes:
  - name: notification-ms
    methods: null
    paths:
    - /notification-ms
    - /ws/notification-ms
    preserve_host: false
    protocols:
    - http
    - https
    regex_priority: 0
    strip_path: false
  plugins:
  - name: cors
    config:
      credentials: true
      exposed_headers:
      - DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization,Upgrade,Access-Control-Allow-Headers,Upgrade,Connection
      headers:
      - DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization,Upgrade,Access-Control-Allow-Headers,Upgrade,Connection
      max_age: 1.728e+06
      methods:
      - GET
      - POST
      - PUT
      - PATCH
      preflight_continue: false
    enabled: true
    run_on: first

BROWSER ERROR***

ERROR:
WebSocket connection to ‘ws://mydomain:8000/ws/notification-ms/421/4galkbf2/websocket’ failed: Error during WebSocket handshake: ‘Upgrade’ header is missing

POST http://mydomain:8000/ws/notification-ms/421/4wyjqxbe/xhr_streaming?t=1560970140560 403

Thanks in advance and great job here awesome technology, regards

#2

You using 1.2.0? If so it’s probably this bug I logged which has been patched but not yet released: https://github.com/Kong/kong/issues/4718

I have another question a couple below yours asking when 1.2.1 will be released.

#3

Hi there,

Thanks for your prompt response. Yes it is version 1.2.0, well I look forward to check new release, regards