[5.x] Allow static warm to use insecure by default with config key #11978
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
Member
|
Are you running this on production? It's already running without ssl verification if your |
Contributor
Author
|
Hey @jasonvarga we use a reverse proxy setup on production environments - so when accessing the site locally, we run into a host of issues, this being one. To completely bypass Cloudflare (which was interrupting our cache warm tasks), we've added the above example to the hosts file, which further complicates SSL verification. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Since it's likely that your entire environment would be "insecure", it only makes sense to be able to configure this globally.
This allows you to set the following in your server's host file and ignore SSL errors: