This repository was archived by the owner on Sep 7, 2021. It is now read-only.
add config parameter exclude_uri_pattern #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
handle redirect after ip-restriction, bot-detection, cors - but before jwt and other authentication plugins
Author
|
BTW. I am adding several commits/updates. If you would like to separate them into different PTs, please tell me. |
only redirect if x-forwarded-for is not set to https
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I would like to be able to install this plugin globally but define the exception explicitly.
Currently, I am only able to decide whether to install the plugin on each route (this might be much work and/or redundancy) or globally. This is inconvenient. E.g. In my case I would like to install it globally - with only one exception: The URL that letsencrypt/certbot uses to validate certificates (
/.well-known/acme-challenge).This PR adds the ability to define the config parameter
exclude_uri_pattern. When this value is empty, then everything is as before (backward compatibility). When it is set, then the redirect to https is only done when the called URI doesn't match to the Lua pattern inexclude_uri_pattern.