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

Timeout handling #100

Open

marcorondong opened this issue Oct 1, 2024 · 1 comment

Assignees

Labels

bug

Collaborator

marcorondong commented Oct 1, 2024

Currently, we close the connection when client reach timeout.
(That causes one of our test to fail)

We should check time and if client timed ot, we shoudl send a response with:

When client is requesting something: 408 Request Timeout.
When ccgi is running and it timed out: 504 Gateway Timeout.

We also should send the header field "Connection: close" so the user-agent close the connection.
Client's time should be refreshed when it request something new.

marcorondong added the bug label

gabrieldanis self-assigned this

Owner

Sekula34 commented Oct 13, 2024

In that case Nginx doesnt send 408, 504 we send.

We maybe should close every time since we are not supporting keep alive
Make sense in keep alive

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment