logging POST request content ?

Hello,

I would like to know if there is a configuration directive that would
allow me to log the content (body) of POST requests. I'm running Apache
2.0 (but I can upgrade to 2.2 if needed).

thaks,

patpro

--
http://www.patpro.net/

In article <slrneu1aa5.3ac.davideyeahsure@fogg.onlyforfun.net >,
Davide Bianchi <davideyeahsure@onlyforfun.net> wrote:

> On 2007-02-24, patpro ~ patrick proniewski <patpro@boleskine.patpro.net>
> wrote:
> > I would like to know if there is a configuration directive that would
> > allow me to log the content (body) of POST requests. I'm running Apache
>
> No, you'll have to alter the source code,

damn... I'm afraid that's not an option for me ;)

> but why?

Because I deny POST to blog spammers, but I would like to collect their
POSTs for analysis.

thanks

patpro

--
http://www.patpro.net/

On 24/02/2007 22:18, patpro ~ patrick proniewski dixit:
> In article <slrneu1aa5.3ac.davideyeahsure@fogg.onlyforfun.net >,
> Davide Bianchi <davideyeahsure@onlyforfun.net> wrote:

>> On 2007-02-24, patpro ~ patrick proniewski <patpro@boleskine.patpro.net>
>> wrote:
>> > I would like to know if there is a configuration directive that would
>> > allow me to log the content (body) of POST requests. I'm running Apache

>> No, you'll have to alter the source code,

> damn... I'm afraid that's not an option for me ;)

>> but why?

> Because I deny POST to blog spammers, but I would like to collect their
> POSTs for analysis.

Intercept them in the script elaborating the form.
It works almost fine.

Cyrus

--
I love to be mailed just by smart people:
perl -we 'print "\12\142\145\162\156\141\155\141\100\151".
"\164\167\145\142\56\151\164\12\12";'
Spammers scratch here with a diamond to find my address:
|||||||||||||||||||||||||||||||||||||||||||||||

In article <mO3Eh.21656$K8.6491@news.edisontel.com>,
cyrusthevirus <root@127.0.0.1> wrote:

> > Because I deny POST to blog spammers, but I would like to collect their
> > POSTs for analysis.
>
> Intercept them in the script elaborating the form.
> It works almost fine.

Doing so would require a modification in the php application, and I
don't want that, I would like something on the Apache side. The spam-bot
interception occurs on the Apache side by the way.
May be there is something to do with the 403 reply, I have to think
about that.

thanks,

patpro

--
http://www.patpro.net/

On 25/02/2007 10:04, patpro ~ patrick proniewski dixit:
> In article <mO3Eh.21656$K8.6491@news.edisontel.com>,
> cyrusthevirus <root@127.0.0.1> wrote:

>> > Because I deny POST to blog spammers, but I would like to collect their
>> > POSTs for analysis.

>> Intercept them in the script elaborating the form.
>> It works almost fine.

> Doing so would require a modification in the php application, and I
> don't want that, I would like something on the Apache side. The spam-bot
> interception occurs on the Apache side by the way.
> May be there is something to do with the 403 reply, I have to think
> about that.


If all the spambots are redirected to a 403 custom page, you can use
this one to grab the data for you statistics.
BTW, which approach are you using for the block?

Cyrus

--
[a directive occurred while processing this error]

In article <DncEh.21696$K8.7168@news.edisontel.com>,
cyrusthevirus <root@127.0.0.1> wrote:

> > May be there is something to do with the 403 reply, I have to think
> > about that.
>
> If all the spambots are redirected to a 403 custom page, you can use
> this one to grab the data for you statistics.

yep, I'm going to create a 403 with an embedded "POST grabber".

> BTW, which approach are you using for the block?

I have to test my settings thoroughly before I can go public with that.
What I can say, is that it involves an unusual way of serving cookies.

patpro

--
http://www.patpro.net/