will always force a DNS lookup, and also force a double reverse
lookup, regardless of the HostnameLookups setting. The result is
the (double reverse checked) hostname, or undef if any of the lookups
fail.

Apache2::Const::REMOTE_HOST

returns the hostname, or undef if the hostname lookup fails. It
will force a DNS lookup according to the HostnameLookups setting.

Apache2::Const::REMOTE_NAME

returns the hostname, or the dotted quad if the hostname lookup fails.
It will force a DNS lookup according to the HostnameLookups
setting.

Apache2::Const::REMOTE_NOLOOKUP

is like Apache2::Const::REMOTE_NAME except that a DNS lookup is never
forced.

The directory config vector from the request. It's needed to find the
container in which the directive HostnameLookups is set. To get one
for the current request use
$r->per_dir_config.

By default, undef is passed, in which case it's the same as if
HostnameLookups was set to Off.

ret: $remote_host ( string/undef )

The remote hostname. If the configuration directive
HostNameLookups is set to off, this returns the dotted decimal
representation of the client's IP address instead. Might return
undef if the hostname is not known.

since: 2.0.00

The result of get_remote_host call is cached in
$c->remote_host. If the latter is set,
get_remote_host will return that value immediately, w/o doing any
checkups.

Normally you should not mess with setting this option when handling
the HTTP protocol. If you do (for example when sending your own
headers set with
$r->assbackwards)
-- take a look at the ap_set_keepalive() function in
httpd-2.0/modules/http/http_protocol.c.

Set the number of served requests over the current
connection. Normally you won't do that when handling HTTP
requests. (But see below a note regarding
$r->assbackwards).

ret: $served (integer)

How many requests were already served over the current connection.

In most handlers, but HTTP output filter handlers, that value doesn't
count the current request. For the latter it'll count the current
request.

since: 2.0.00

This method is only relevant for keepalive
connections. The core connection output filter
ap_http_header_filter increments this value when the response
headers are sent and it decides that the connection should not be
closed (see ap_set_keepalive()).

If you send your own set of HTTP headers with
$r->assbackwards,
which includes the Keep-Alive HTTP response header, you must make
sure to increment the keepalives counter.

Apache2::Connection also provides auto-generated Perl interface for
a few other methods which aren't tested at the moment and therefore
their API is a subject to change. These methods will be finalized
later as a need arises. If you want to rely on any of the following
methods please contact the the mod_perl development mailing list so we can help each other take the steps necessary
to shift the method to an officially supported API.