If you'd like to send me his reply to contact(at)wpmudev.org with the subject line Attn: Jack Kitterhing and I'd be happy to take a look for you :)
I've been looking for an article for you, but unfortunately there doesn't appear to be one!
It's quite insecure on a shared hosting environment, where a loopback connection can cause a security issue with the connections on a shared hosting, it's more secure on a dedicated hosting, where it can be correctly secured and doesn't risk bringing down other sites on the hosting.
This is the most common reason a shared host disables it, due to the risk to other sites.
You are correct that is is required by WordPress to run the cron process and upgrades etc.
Many sites do have it enabled, it's mostly disabled on some shared hosting :)
If you'd like to send me his reply to contact(at)wpmudev.org with the subject line Attn: Jack Kitterhing and I'd be happy to take a look for you :)
I've been looking for an article for you, but unfortunately there doesn't appear to be one!
It's quite insecure on a shared hosting environment, where a loopback connection can cause a security issue with the connections on a shared hosting, it's more secure on a dedicated hosting, where it can be correctly secured and doesn't risk bringing down other sites on the hosting.
This is the most common reason a shared host disables it, due to the risk to other sites.
You are correct that is is required by WordPress to run the cron process and upgrades etc.
Many sites do have it enabled, it's mostly disabled on some shared hosting :)
การแปล กรุณารอสักครู่..