Vipergts450 custom ___location patch #1081
Merged
+54
−3
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.
Possibly resolves jc21#148 jc21#590 but needs a lot of testing as I roughed this together. Probably can replace the top block with a modified
include conf.d/include/proxy.conf;
Allows custom locations to follow the rules set on the primary page such as Websockets, forcing SSL, HSTS, etc.
Made a couple of amendments to
/backend/templates/_location.conf
and/backend/internal/nginx.js
to allow the custom ___location templates to have includes which should flesh out their configs and follow the settings of the main configuration page. Needs a lot of testing.