Adds modsecStatusEngineCall to standalone API

In ModSecurityIIS the configuration is loaded upon the first request
is received. In other words, SecStatusEngine value can be only
loaded once the first request hit the server, and so, the status
function was moved to proceed just after the configuration got loaded.
This update is IIS only.
This commit is contained in:
Felipe "Zimmerle" Costa
2014-02-15 00:29:51 -02:00
committed by Felipe Zimmerle
parent d75e443b9b
commit 20014c808c
6 changed files with 28 additions and 2 deletions

View File

@@ -701,3 +701,16 @@ const char *modsecIsServerSignatureAvailale(void) {
return new_server_signature;
}
#ifdef WIN32
void modsecStatusEngineCall()
{
if (status_engine_state != STATUS_ENGINE_DISABLED) {
msc_status_engine_call();
}
else {
ap_log_error(APLOG_MARK, APLOG_NOTICE, 0, NULL,
"Status engine is currently disabled, enable it by set " \
"SecStatusEngine to On.\n");
}
}
#endif

View File

@@ -119,6 +119,10 @@ void modsecSetConfigForIISRequestBody(request_rec *r);
const char *modsecIsServerSignatureAvailale(void);
#ifdef WIN32
void modsecStatusEngineCall(void);
#endif
#ifdef __cplusplus
}
#endif