Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improvements for lock handling #1041

Open
Acconut opened this issue Dec 5, 2023 · 0 comments
Open

Improvements for lock handling #1041

Acconut opened this issue Dec 5, 2023 · 0 comments
Assignees
@Acconut

Comments

@Acconut
Copy link
Member

Acconut commented Dec 5, 2023

When a PATCH request is interrupted by another (HEAD) request, the first request is currently stopped and a response is immediately sent. For HTTP/1.1 this causes the connection to be closed and the response is not available for browsers, for example.

We should

  • investigate how this behaves with HTTP/2 and HTTP/3 which supports full duplex modes.
  • investigate if we should leave the first PATCH request running, so that client competitions as reported in @tus/server: add support for lockers tus-node-server#514 (comment) are avoided.
  • investigate how this behaves with proxies (e.g. do we need to adjust Keep-Alive mechanisms?)
@Acconut Acconut self-assigned this Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Acconut Acconut

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Acconut