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

Deploying G6 at K8s fails due to HTTP 2 keep alive problem #779

Open
bloodbare opened this issue Dec 17, 2019 · 2 comments
Open

Deploying G6 at K8s fails due to HTTP 2 keep alive problem #779

bloodbare opened this issue Dec 17, 2019 · 2 comments
Labels
bug
Milestone
G6

Comments

@bloodbare
Copy link
Member

More information:

encode/uvicorn#344
@bloodbare bloodbare added the bug label Dec 17, 2019
bloodbare added a commit that referenced this issue Dec 17, 2019
@bloodbare
Fixing #779 by settings http protocol and allowing to set keep alive …
9ea8853 
…timeout
@vangheem
Copy link
Member

dang, I saw this sort of thing with ambassador/envoy as well :(

bloodbare added a commit that referenced this issue Dec 17, 2019
@bloodbare
Merge pull request #780 from plone/http11
65a06d7 
Fixing #779 by settings http protocol and allowing to set keep alive …
@jordic
Copy link
Contributor

jordic commented Dec 17, 2019

Perhaps, this doesn't happens to us because we are using caddy (go based). Is envoy perhaps based on the same http lib than nginx?

@bloodbare bloodbare added this to the G6 milestone Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
G6
Development

No branches or pull requests
3 participants
@jordic @bloodbare @vangheem