**SPIP**
# Article submitted
The article "**\_HTML\_BG\_CRON\_FORCE**
(https://www.spip.net/ecrire/?exec=article&id_article=6583)" is submitted
for publication. on Monday 8 June 2020.
* * *
## \_HTML\_BG\_CRON\_FORCE
Monday 8 June 2020 , by [jack](.././?page=auteur&id_auteur=593&)
The constant **`_HTML_BG_CRON_FORCE`** inhibits cron release by
fsockopen/cURL.
The constant **`_HTML_BG_CRON_FORCE`** (*available since SPIP 3.0.14*)
responds to the problem found on some servers whose firewall is set to
silently DROP any outgoing http request: fsockopen then waits 30s to launch
the request at each hit before giving back the hand. cURL does not wait for
it but does not know that its request fails. Result the CRON never runs and
the site has a catastrophic response time...
If you know that you are on such a configuration (and that you cannot
change it) it is possible to define the value of the constant
`_HTML_BG_CRON_FORCE` in your file
`config/mes_options.php` (See the article dedicated to it
(https://www.spip.net/ecrire/?exec=article&id_article=4909)).
Example :
// to greatly reduce site response times,
// do not throw the cron by fsockopen/cURL
// because the server configuration does not allow it.
define
(http://www.php.net/define)
(
'_HTML_BG_CRON_FORCE'
,
TRUE
)
;
This setting also restores the operation of CRON tasks in case your site is
protected by a pair of files **.htaccess** / **.htpasswd** (see constant
\_DIRECT\_CRON_FORCE
(https://www.spip.net/ecrire/?exec=article&id_article=6582)).
— Sent by SPIP (https://www.spip.net/)
