Chris Lewis wrote:
[Given that Stronghold is a bit old, I'm endeavering to build
Apache/mod_ssl/mod_perl from scratch, but it complains about not being
able to load Apache.pm... Is there a step-by-step set of Solaris
instructions somewhere?]
Maybe following helps:
On Thu, 28 Sep 2000, Chris Lewis wrote:
It works to proxy the HTTP to the system fine, however, POST parameters
seem to get mangled and/or truncated.
they should get passed through by mod_proxy, provided nobody else has read
the POST data first.
When I try to reference $r-content the
Doug MacEachern wrote:
On Thu, 28 Sep 2000, Chris Lewis wrote:
It works to proxy the HTTP to the system fine, however, POST parameters
seem to get mangled and/or truncated.
they should get passed through by mod_proxy, provided nobody else has read
the POST data first.
When I try
I figured out what it was. One of the $r-header_in() was trying to
insert an Authorize header, and I didn't notice that base64_encode()
tacks on a newline.
After Apache core got thru with it, it ended up looking like:
Authorize: Basic \n
\r\n
\r\n
I'm writing a perl trans handler to invoke mod_proxy for non-proxy
requests.
Stronghold 3 on Solaris 2.6, server announces:
Stronghold/3.0 Apache/1.3.12 C2NetEU/3011 (Unix) PHP/3.0.16
mod_ssl/2.6.4 OpenSSL/0.9.5a mod_perl/1.22
I'm essentially using the code from page 371 of the Eagle book
