Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #353 - Allow insecure curl reqs for cron #450

Merged
merged 1 commit into from
Dec 29, 2015

Conversation

swalkinshaw
Copy link
Member

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.

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.
@swalkinshaw swalkinshaw force-pushed the fix-curl-insecure-reqs branch from 614f622 to 308b55a Compare December 29, 2015 02:40
swalkinshaw added a commit that referenced this pull request Dec 29, 2015
Fix #353 - Allow insecure curl reqs for cron
@swalkinshaw swalkinshaw merged commit 7e14cc9 into master Dec 29, 2015
@swalkinshaw swalkinshaw deleted the fix-curl-insecure-reqs branch December 29, 2015 03:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant