Lines Matching refs:format

112  * APLOGNO() should be used at the start of the format string passed
323 * and ap_log_perror use a printf style format string to build the log message.
325 * such as the request-URI or request header fields, within the format
327 * attack and other messy behavior. Instead, use a simple format string
333 * request or connection. This uses a printf-like format to log messages
341 * @param fmt The format string
351 * the format string. Doing so makes the server vulnerable to a
353 * simple format string like "%s", followed by the string containing the
375 __attribute__((format(printf,7,8)));
381 * format to log messages to the error_log.
388 * @param fmt The format string
394 * the format string. Doing so makes the server vulnerable to a
396 * simple format string like "%s", followed by the string containing the
417 __attribute__((format(printf,7,8)));
422 * request. This uses a printf-like format to log messages to the
430 * @param fmt The format string
436 * the format string. Doing so makes the server vulnerable to a
438 * simple format string like "%s", followed by the string containing the
459 __attribute__((format(printf,7,8)));
464 * connection. This uses a printf-like format to log messages to the
472 * @param fmt The format string
480 * the format string. Doing so makes the server vulnerable to a
482 * simple format string like "%s", followed by the string containing the
503 __attribute__((format(printf,7,8)));
509 * printf-like format to log messages to the error_log.
517 * @param fmt The format string
526 * the format string. Doing so makes the server vulnerable to a
528 * simple format string like "%s", followed by the string containing the
552 __attribute__((format(printf,8,9)));
557 * and ap_log_csdata log a buffer in printable and hex format. The exact
558 * format is controlled by processing flags, described next.