-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
nixos/nginx: make redirect status code configurable #271506
nixos/nginx: make redirect status code configurable #271506
Conversation
fbde713
to
f2b5067
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some nits
f2b5067
to
7230f20
Compare
7230f20
to
c2879c5
Compare
c2879c5
to
9dd5d41
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, we only need you to add yourself to meta.maintainers of the redirect code test.
9dd5d41
to
9f629ae
Compare
Thanks! Added myself as a maintainer on the test |
Ideally, if you can add a note in the release notes about this new option, that'd be great, then we can go for the merge. |
9f629ae
to
e6d036d
Compare
Add an option to configure which code globalRedirect and forceSSL use. It previously was always 301 with no easy way to override.
e6d036d
to
a3c60d2
Compare
Thanks, @RaitoBezarius! Added an entry to the changelog. |
Description of changes
Currently, both globalRedirect and forceSSL always use 301, with no easy way to change it through services.nginx options. This PR adds an option to configure it.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Priorities
Add a 👍 reaction to pull requests you find important.