-
Notifications
You must be signed in to change notification settings - Fork 150
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.
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
clone via HTTP fails #427
Comments
This is due to having a _set_ value of Read/Write http server timeout values, and a faulty git gzip request handler. Replace the read/write timeouts with idle timeout which is only used when keep-alive is enabled. That is the case by default. Fix git by properly handling gzip and buffered git service responses. Improve git http handler logging Fixes: #427
This was due to having a _set_ value of Read/Write http server timeout values, and a faulty git gzip request handler. The server drops the connection if there wasn't any read/write within 10 seconds. Replace the read/write timeouts with idle timeout which will reset the counter to _either_ read/write within 10 seconds. Idle timeout is only used when keep-alive is enabled. That is the case by default. Fix git by properly handling gzip and buffered git service responses. Improve git http handler logging Fixes: #427
This was due to having a _set_ value of Read/Write http server timeout values, and a faulty git gzip request handler. The server drops the connection if there wasn't any read/write within 10 seconds. Replace the read/write timeouts with idle timeout which will reset the counter to _either_ read/write within 10 seconds. Idle timeout is only used when keep-alive is enabled. That is the case by default. Fix git by properly handling gzip and buffered git service responses. Improve git http handler logging Fixes: #427
Hi @nomas2000, thank you very much for reporting this issue. After some debugging, I found the culprit. Soft Serve HTTP server has a read timeout of 10 seconds, and it closes the connection since the repo is taking too long to read. Nevertheless, it was also handling gzip incorrectly which is the default compression This now should be fixed in #428, feel free to test it out and report back 🙂 |
If you fixed it, release it. |
This was due to having a _set_ value of Read/Write http server timeout values, and a faulty git gzip request handler. The server drops the connection if there wasn't any read/write within 10 seconds. Replace the read/write timeouts with idle timeout which will reset the counter to _either_ read/write within 10 seconds. Idle timeout is only used when keep-alive is enabled. That is the case by default. Fix git by properly handling gzip and buffered git service responses. Improve git http handler logging Fixes: #427
soft-serve running on AlmaLinux9 (ie. redhat)
a large repo (that I want to mirror) works via SSH, but "fails" via HTTP
... other (smaller?) repos seem to work via HTTP
Attached (log) file shows launching fresh container and then:
installing soft-serve, importing a big-repo, and 'git clone http://...' fails with 500-err
... rerun the steps to reproduce the err ...
Did not see helpful err-msgs w/ *DEBUG* enabled (logs below are from previous week)
soft-serve-alma9-container-large-repo.txt
The text was updated successfully, but these errors were encountered: