httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devin L. Ganger" <>
Subject Re: [users@httpd] Problems compiling mod_proxy_html with Apache 2.1.3-beta
Date Wed, 06 Apr 2005 18:02:44 GMT
on 4/6/2005 10:34 AM Nick Kew wrote:

> Devin L. Ganger wrote:

>>I'm trying to build a full reverse proxy that can properly handle the
>>cookies from my back-end systems.

>>My system is running Solaris 9/SPARC, gcc 3.4.2, with the following

> I've compiled it on Solaris at least on the sourceforge server farm
> without problem.

Yeah, I didn't think Solaris 9/SPARC would be an unknown...

>>At first I tried using Apache 2.0.53 with Nick Kew's mod_proxy_html.c
>>add-on, as well as his patch to mod_proxy to support the
>>ProxyPassReverseCookieDomain and ProxyPassReverseCookiePath directives.
>>When I tried to apply the patch to the source, it failed to apply cleanly.

> The patch from bugzilla?  What didn't work?

$ patch -i mod_proxy.c.patch -o mod_proxy.c
   Looks like a unified context diff.
Hunk #5 failed at line 50.
Hunk #6 failed at line 159.
Hunk #7 failed at line 122.
Hunk #8 failed at line 643.
Hunk #9 failed at line 651.
Hunk #10 failed at line 662.
Hunk #11 failed at line 733.
Hunk #12 failed at line 746.
Hunk #13 failed at line 754.
Hunk #14 failed at line 767.
Hunk #15 failed at line 803.
11 out of 15 hunks failed: saving rejects to mod_proxy.c.rej
   I can't seem to find a patch in there anywhere.

If you want, I can show you the mod_proxy.c.rej file (although I don't 
think it'll help you much).

>>mod_proxy_html.c:91: error: parse error before "regex_t"

> I guess you may need some additional #include for regexps on your box.
> The rest of the errors look like a cascade from that.

Both Apache 2.0.53 and 2.1.3-beta seem to find it just find, though, 
whether I specify the external PCRE libraries or not. (I've tried moving 
the relevant include and library files out of the way during compilation 
so that I know they're not being found.)

If Apache was using a built-in regex library and includes, shouldn't the 
apxs environment already include the necessary directives? That's what 
bothers me about this; Apache compiles without any problems whatsoever, 
and both your patch and module are completely straightforward. I'm not 
doing something stupid like trying to compile the module from the wrong 
directory, am I?

Devin L. Ganger <>
"Aikido is based around the central precept of letting an attack take
its natural course.  You, of course, don't want to impede that natural
flow by being in its way." -- overheard on the PyraMOO

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message