|Did you know ...||Search Documentation:|
|library(http/http_log): HTTP Logging module|
Simple module for logging HTTP requests to a file. Logging is enabled
by loading this file and ensure the setting http:logfile is not the
empty atom. The default file for writing the log is
library(settings) for details.
The level of logging can be modified using the multifile predicate
http_log:nolog/1 to hide HTTP request
fields from the logfile and
http_log:password_field/1 to hide
passwords from HTTP search specifications (e.g.
appendmode if the file is not yet open. The log file is determined from the setting
http:logfile. If this setting is set to the empty atom (''), this predicate fails.
If a file error is encountered, this is reported using print_message/2, after which this predicate silently fails.
Before opening the log file, the message
is broadcasted. This message allows for creating the directory,
renaming, deleting or truncating an existing log file.
server(Reason, Time). to the logfile. This call is intended for cooperation with the Unix logrotate facility using the following schema:
Content-typeheader. If the hook succeeds, the POST data is not logged. For example, to stop logging anything but application/json messages:
:- multifile http_log:nolog_post_content_type/1. http_log:nolog_post_content_type(Type) :- Type \= (application/json).
|Type||is a term MainType/SubType|
library(http/http_unix_daemon)is used, closing is achieved by sending SIGHUP or SIGUSR1 to the process.
library(http/http_unix_daemon)which schedules the maintenance actions.
true, rotate the log files in the background.
This must be used with a timer that broadcasts a
maintenance(_,_) message (see broadcast/1).
Such a timer is part of