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.

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

nginx service: Make http2 an option. #32858

Merged
merged 1 commit into from Dec 20, 2017
Merged

Conversation

nh2
Copy link
Contributor

@nh2 nh2 commented Dec 19, 2017

HTTP 2 can break some things, for example due to this Chrome bug:

https://bugs.chromium.org/p/chromium/issues/detail?id=796199

So the service hardcoding it to be enabled is not helpful.

This commit adds an option so you can turn it off.

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Fits CONTRIBUTING.md.
  • Tested in my nginx staging deployment

CC @fpletz @globin

HTTP 2 can break some things, for example due to this Chrome bug:

  https://bugs.chromium.org/p/chromium/issues/detail?id=796199

So the service hardcoding it to be enabled is not helpful.

This commit adds an option so you can turn it off.
Copy link
Member

@fpletz fpletz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thanks! 👍

@fpletz
Copy link
Member

fpletz commented Dec 19, 2017

We should IMHO also backport this simple new option to 17.09.

@nh2
Copy link
Contributor Author

nh2 commented Feb 14, 2018

HTTP 2 can break some things, for example due to this Chrome bug:

https://bugs.chromium.org/p/chromium/issues/detail?id=796199

It turned out not to be a bug in Chrome, but in nginx. The bug now contains updated information.

I'll open an issue to discuss whether we should change an nginx setting that works around this, as it is affecting all browsers and HTTP/2 is on by default on NixOS.

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

Successfully merging this pull request may close these issues.

None yet

3 participants