Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • slapos slapos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Merge requests 129
    • Merge requests 129
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedinexedi
  • slaposslapos
  • Merge requests
  • !1911

Draft: Fix/rapid cdn assure http1.1 websocket client origin

  • Review changes

  • Download
  • Patches
  • Plain diff
Open Łukasz Nowak requested to merge luke/slapos:fix/rapid-cdn-assure-http1.1-websocket-client-origin into master Oct 20, 2025
  • Overview 0
  • Commits 0
  • Pipelines 0
  • Changes -

When websocket is used it shall be assured that CDN will only use HTTP/1.1 from the client and to the backend, as this will lead to problems. The CDN shall assure such scenario, even if the cluster or slave is using other protocol versions (especially HTTP/2 or HTTP/3).

Also websocket have to be fully tested on the full chain, from the client to the origin, including cached slaves.

Backend needs to be at least like https://echo.websocket.org/ , the client shall be recurls, with eventual improvements to allow it play with websocket directly to make assertions.

Inspire from https://websockets.readthedocs.io/en/stable/

Edited Nov 06, 2025 by Łukasz Nowak
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: fix/rapid-cdn-assure-http1.1-websocket-client-origin
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7