Introduce TRUSTED_HOSTS and CADDY_MERCURE_PUBLIC_URL variables #591
Conversation
This file contains 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
…_URL variables Fix issue with invalid TRUSTED_HOSTS and MERCURE_PUBLIC_URL when using http://localhost or :80 as SERVER_NAME
maxhelias
approved these changes
Mar 19, 2024
|
@J3m5 yes please! |
dunglas
approved these changes
Mar 19, 2024
The instructions has been added to the TLS documentation page. |
maxhelias
approved these changes
Apr 18, 2024
|
Thanks @J3m5 ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix issue with invalid
TRUSTED_HOSTSandMERCURE_PUBLIC_URLwhen usinghttp://localhostor:80asSERVER_NAMEvalueFollow up of api-platform/api-platform#2666
Should I add a note in the docs @dunglas?