Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • slapos slapos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 124
    • Merge requests 124
  • 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
  • nexedi
  • slaposslapos
  • Merge requests
  • !1911

Open
Created Oct 20, 2025 by Łukasz Nowak@lukeMaintainer
  • Report abuse
Report abuse

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

  • Overview 0
  • Commits 0
  • Changes 0

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.

Edited Oct 20, 2025 by Łukasz Nowak
Assignee
Assign to
Reviewer
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