Fix #353 - Allow insecure curl reqs for cron #450
Merged
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.
In development with an https site, the curl command for WP cron will
fail due to the "insecure" self-signed certificate.
Adding the
-k
flag means curl will ignore this and continue on.Note: there's no real downside/risk to using this option on staging/production as well. These are your own sites and internal requests. This curl command should not be the thing that tells you if your SSL setup isn't correct.