[ale] Q: getting details on POSTs to Apache

[James Sumners]

<?php
print('<pre>'); print_r($_REQUEST); print('</pre>');
?>

On 6/26/06, Mills, John M. <Mills.J at ems-t.com> wrote:
> ALErs -
>
> I'm going over the 'Log Files' doc for Apache-1.3 and not finding quite
> what I need. My server receives 'POST' messages from clients which
> provide a few text strings as args to set variables. I have just enabled
> Apache's logging against the 'out-of-the-box' "combined" log definition
> in 'httpd.conf':
>
> # a CustomLog directive (see below).
> LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\""
> combined
>  ...
> # (Combined Logfile Format) you can use the following directive.
> CustomLog /tmp/web_access_log combined
>  ...
>
> These settings get me the source, destination, and action corresponding
> to a 'POST', but not the names and values it has returned. The POSTs are
> processed by a PHP script that can echo the values it receives, but not
> the list of [name:value] of whatever came from the client (or at least
> _I_ don't know how to dump that information).
>
> I'm missing the link of seeing content of each POST as it goes by
> Apache.
>
> Is there an Apache log setting that would dump incoming messages' full
> contents to the log? I guess I could install 'ipchains' (this is a
> small, old configuration), but getting the information out of Apache
> would be easier.
>
> TIA.
>  - Mills
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>


-- 
James Sumners
http://james.roomfullofmirrors.com/

"All governments suffer a recurring problem: Power attracts
pathological personalities. It is not that power corrupts but that it
is magnetic to the corruptible. Such people have a tendency to become
drunk on violence, a condition to which they are quickly addicted."

Missionaria Protectiva, Text QIV (decto)
CH:D 59