- Issue created by @cmlara
- 🇺🇸United States drumm NY, US
We have been investigating this as GitLab has been increasingly using this WebSocket.
Our CDN does not support web sockets by default. I believe we have that capability enabled now. The next steps are to verify this and make any necessary configuration changes. It hadn’t made it to the top of the priority list due to DrupalCon Barcelona preparation and other tasks.
- 🇺🇸United States drumm NY, US
The CDN configuration to passthrough websocket connections to our origin is now in place. The websocket requests now look like they are connecting successfully.
I fully expect more adjustments will be needed as we monitor.
- 🇺🇸United States cmlara
I can confirm I'm no longer seeing 404's on the web sockets and ping messages appear to be processing unobstructed allowing the UI to adjust as needed to changes in an MR pipeline.
Appears reasonable to call this RTBC as is. Any other errors can be raised as a new issue.
- 🇺🇸United States drumm NY, US
Yes, I think we can call this done. It looks like connections are initiating and being held open for a reasonable amount of time.
Automatically closed - issue fixed for 2 weeks with no activity.