urlcp settings control various informational
and trace behaviors. Note that increasing these settings may cause
sensitive information to be printed and/or sent to
e.g. authentication or password data.
badheadermsgs(boolean) Whether to issue a
putmsgfor malformed response headers. Added (and defaults to on) in version 5.01.1102538511 20041208. Returns previous setting.
charsetmsgs(boolean) Whether to issue a
putmsgfor charset conversion problems. The default is on. Added in version 5.00.1089408135 20040709. Returns previous value.
cookiemsgs(boolean) If true, additional messages are printed when invalid cookies are received and discarded, via the
putmsgmechanism (here). If false (default), invalid cookies are silently discarded. Returns previous setting. Added in version 4.01.1022000000 20020521. See also the Cookies section (here).
fetchmeter(boolean or string) Whether to print a progress meter during fetches. If true, a hash-mark progress meter is printed for uploads and downloads, where possible. The setting can also be a meter type: one of "
percent" or "
none". A true value enables a meter of type "
simple". Returns previous value. Added in version 6.
putmsg pass|save|all|clear [on|off [on|off ...]](boolean) Controls the disposition of
putmsgs from fetches. The first argument is a boolean action, which is set to the corresponding boolean value from the second (or later) value argument:
pass: Whether to pass fetch-related messages through to the normal
putmsgmechanisms, i.e. printing, logging and/or
<putmsg>function (if enabled). Since messages can also be saved for later return via
<urlinfo>, this is often turned off to prevent the need for duplicate handlers. Non-fetch messages (
<sql>, etc) are unaffected by this. On by default.
save: Whether to save messages in a buffer for later retrieval with <urlinfo putmsgs>. Calling <urlinfo putmsgs> inside a <fetch parallel> loop will return only the messages for the just-completed fetch, making disambiguation of messages easier than with the normal script
<putmsg>function callback mechanism. On by default.
save(in that order) according to the next value argument values.
clear: Clear the current fetch putmsg buffer. No arguments.
Returns the previous setting(s) (two values if
putmsg setting was added in version 6.
redirmsgs(boolean) If true, info messages about redirects will be printed (via the
putmsgmechanism). If false (default), such messages are suppressed.
In version 7.01.1385154000 20131122 and later, an integer value is
interpreted as a set of bit flags controlling which types of
errors to report: flag
0x1 for ordinary script errors, flag
assert() failures (which were unreported
prior to version 7.00.1372360000 20130627). String boolean values
now set all flags on or off.
traceauth(integer) Set trace message level for client/server authentication calls. Value is a bitwise OR of any of the following flag values; the default is 0 (i.e. no tracing):
Keep-Alive(persistent connections) messages
traceauthvalues changed in version 7.06.1465245000 20160606.
tracecalls(integer) Set trace message level for fetch-related function calls. This is a bitwise OR of integer values indicating which calls to issue messages for; the default is 0 (i.e. no tracing):
Set trace message level for DNS (IP address parsing and hostname lookup) calls. In version 7.07.1553195000 20190321 and later, the value is a bitwise OR of integer values:
In versions prior to 7.07.1553195000 20190321, the value was an incrementing integer, i.e. each level provides messages at its level and all preceding levels; the default is 0 (i.e. no tracing):
gethostbyaddr()calls; miscellaneous warnings
traceencoding(integer) Sets trace message level for content and transfer encoding calls. Value is a bitwise OR of any of the following flags; the default is 0 (i.e. no tracing):
tracefetch(integer) Set trace message level for fetch library calls. Value is a bitwise OR of any of the following flags; the default is 0 (i.e. no tracing):
Added in version 5.01.1147127000 20060508. Bit 0x0080 added in version 6.00.1308203000 20110616. Bit 0x0100 added in version 7.04.1446832000 20151106. Bits 0x200 - 0x2000 added in version 7.06.1471876000 20160822. Setting 0x3e03 should trace all network activity. Values may change or be added to in future releases.
traceskt(integer) Set trace message level for socket (i.e. over-the-wire network traffic) calls. Value is a bitwise OR of any of the following flag values; the default is 0 (i.e. no tracing):
verbose(integer) Sets the verbosity level; used for debugging. This is a bitwise OR of integer values indicating what high-level protocol information to print:
A "small" flag prints only up to 16 lines of the content; a
"medium" flag only up to 128 lines; both together print the
entire document. Note that the raw document is the "payload"
document as returned by
<urlinfo rawdoc>, i.e. after
transfer/content encodings have been removed.
Previous to version 5.01.1093600000 20040826 the
setting was an incrementing integer, 0 to 2. Previous to version
7.07.1545428000 20181221 only the request/response lines/headers
flags existed, and were 4x (2 bit positions) smaller. Some flags
unsupported in some conditions, e.g. document flags are generally
unsupported when the document is coming from or going to a file
Note: Setting a non-zero verbosity level may also print sensitive data such as authentication or password strings.