Skip to content

extenginx: Fix redirect to https port#35

Merged
theyoyojo merged 1 commit into
masterfrom
http_cleanup
Mar 20, 2024
Merged

extenginx: Fix redirect to https port#35
theyoyojo merged 1 commit into
masterfrom
http_cleanup

Conversation

@charliemirabile

Copy link
Copy Markdown
Contributor

putting the return directive at the top level means that all processing immediately stops (including location directives), so as written, it was impossible to actually add snippets to the http server that do anything.

Moving the return statment into a location / block will allow it to continue to function as a fallback, but allows more specific overrides to be provided with additional location blocks in included snippets.

putting the `return` directive at the top level means that
all processing immediately stops (including location directives),
so as written, it was impossible to actually add snippets to
the http server that do anything.

Moving the return statment into a `location /` block will allow it to
continue to function as a fallback, but allows more specific overrides
to be provided with additional location blocks in included snippets.

@theyoyojo theyoyojo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Tested that this doesn't break existing redirect behavior

@theyoyojo theyoyojo merged commit 6ccc1de into master Mar 20, 2024
@theyoyojo theyoyojo deleted the http_cleanup branch March 20, 2024 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants