apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Wells" <awe...@cd-crafters.com>
Subject Re: POST to SSI? [was: Using APR]
Date Sun, 22 Aug 2004 23:17:17 GMT

Thanks for the info.

Didn't know if you have seen this thread from the mod_perl mailing list?


I found it of particular interest given what I am trying to accomplish.  I
also wanted to iterate that I'm trying to design my approach to this problem
so as not to brake anything down the request chain.  In short,  I'm wanting
to pass an input socket in place of the real socket for each request down
the chain.  This way, any generators, filters, etc won't blow-up when they
attempt to read the POST data themselves.

I'm not sure if my recent installation of Apache 2 has been built around
libapreq-2.  I am using DSO, so this may not be a problem for my custom

Course, I am wondering, if I do use apreq-2 to parse the POST data, how do I
then pass this POST data to the subrequest which is definitly headed for
mod_jk2?  Did I miss something in the apreq-2 function list?

Since there are so many who wish to pass the POST data around the request
chain, I think it would be a wise choice for apreq to become the "required"
data handler.

Geesh, I didn't know what I was getting into with this project!!!


----- Original Message -----
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
To: <o.d.charbonnier@oxys.net>
Cc: <apache-modules@covalent.net>; "Anthony Wells" <awells@cd-crafters.com>
Sent: Sunday, August 22, 2004 2:57 PM
Subject: Re: POST to SSI? [was: Using APR]

> At 05:09 AM 8/22/2004, you wrote:
> >On Sun, 22 Aug 2004, Cliff Woolley wrote:
> >
> >To the OP in reply to your direct contact explaining more about your
> >problem, you might want to look at the input filter in mod_security,
> >which does something broadly similar.  But if you want to POST to SSI
> >you've got a simpler, more fundamental issue to deal with: the default
> >handler - the one that just sends a file - doesn't accept POST.  If your
> >data are not large, a simple handler that converts the data to GET
> >and does an internal redirect might be a simpler workaround.
> Or investigate a method to enable apreq-2 parsing of the post/get
> data for mod_include.  It might be slick to roll apreq-2 as the
> recommended get/post variable handling for httpd-2.2 - I really
> suspect this is the simplest approach, Anthony.
> Bill

View raw message