<[EMAIL PROTECTED]> writes:
> What if you wanted the functionality of the fase handlers before and after
> the loading of the file..
>
> Could this also be accomplished by proper use of configuration statements
> in http.conf?
> Right now I do not think so, so getting the child tied up for the time
> of the upload I take for granted.
>
I'm not quite sure what your driving at. Let me see if I can
describe how things work now, and what I'm trying to accomplish with the
patch.
Setup:
A = mod_proxy enabled front-end server;
keepalives enabled
delivers static content (images, stylesheets, etc)
proxies dynamic content
B = mod_perl server; responsible for dynamic content;
keepalives disabled
Z = browser
Event:
1) Z requests a dynamic page from A.
Z -GET 1.1-> A -PROXY-> B -PROXY-> A -CLOSE-> Z
The current mod_proxy CLOSES the connection from A to Z,
even if Z requests keepalives, and A implements them. This
is bad since subsequent requests for static content (images/stylesheets,etc.)
will require a new connection.
The patch should prevent mod_proxy from forcibly closing the
A-Z connection.
2) Z posts form data that will ultimately be handled by B.
Z -POST-> A ->PROXY-> B
Currently, mod_proxy opens the connection to B as soon as it
determines B is the ultimate destination. As the POST data
is read from Z to A, it is passed along directly to B. This
will tie up both A and B if the A-Z connection is slow and/or
the post data is huge.
The patch makes mod_proxy buffer the post data in a temp file
by setting the (new) ProxyPostMax directive to a positive number.
If the Content-Length header supplied by Z is greater than this
number, mod_proxy rejects the post request.
Once the post data has been uploaded from Z->A, the patched
mod_proxy opens the connection to B and delivers the POST data
directly from the temp file.
That's what I'm trying to accomplish with the mod_proxy patch.
I've done only minimal testing on http requests; https is NOT
implemented at all.
I'd need something like this implemented, since I use mod_perl
for authenticating "POSTers". In my case the POST data must
be processed by the mod_perl server.
Any help/suggestions are welcome and appreciated!
--
Joe Schaefer
[EMAIL PROTECTED]
SunStar Systems, Inc.
