Just for interest:
was is the current status of httpd-2.0?
Will 2.0.65 be released (soon)?
When is it planned to mark httpd-2.0 as EOL?
Hi,
I think there is an issue in mod_slotmem_shm / mod_proxy_balancer
with httpd 2.4.x when building and installing as root, but trying
to run httpd as standard unix-user.
Scenario:
my httpd is installed as 'root' in /root/httpd-2.4.1/, permissions
root:root/0755. When I create a 'user' httpd.con
lotmem_shm / mod_proxy_balancer (AH01179)
What system is this... I'm assuming that your shm impl does an
actual file connection for the shm instance...
On Mar 5, 2012, at 10:46 AM, Zisis Lianas wrote:
> Hi,
>
> I think there is an issue in mod_slotmem_shm / mod_proxy_balancer
> with ht
Thanks Jim, that works fine for the default-rel-runtimedir configuration.
Slotmem file is created as /logs/slotmem-shm-s.shm.
Now if also the slotmem-file-target-location directive gets available,
this thread is done for me.
Regards,
Zisis
- Original Message -
From: "Jim Jagiels
"Jim Jagielski"
To: dev@httpd.apache.org
Sent: Tuesday, March 6, 2012 7:26:19 PM
Subject: Re: httpd 2.4.1 and mod_slotmem_shm / mod_proxy_balancer (AH01179)
My plan is 2 pronged... to see if r1297560 is enough and if
allowing a slotmem override is even needed (or wanted) ... ;)
On Mar
ough and if
allowing a slotmem override is even needed (or wanted) ... ;)
On Mar 6, 2012, at 12:35 PM, Zisis Lianas wrote:
> Thanks Jim, that works fine for the default-rel-runtimedir configuration.
> Slotmem file is created as /logs/slotmem-shm-s.shm.
>
> Now if also
hi,
when mod_proxy currently is generating his "id", the name
of this id is not very unique. So if you have a shared config/
logs dir for more instances, the slotmem-shm files generated in
DefaultRuntimeDir are the same. Bit unlucky if working with shared
file systems.
In httpd-2.4.2/modules/prox
Hi,
when setting ProxyErrorOverride to "On" to get the httpd-ErrorDocument
instead of the backend-errordoc, httpd is waiting "ProxyTimeout" seconds
to respond to the client, even though the response is already read from
backend server.
The request/response is hanging somewhere in
module/proxy/m
ttpd.apache.org
Sent: Tuesday, May 1, 2012 8:43:46 PM
Subject: Re: httpd 2.4.2 - mod_proxy id name not unique
Let me look into that... iirc, it was due to us wanting to
be able to persist data between restarts and using the time
as part of the id prevented that. But I could be mis-remembering.
Hi guys,
when using proxy balancer configuration ("
BalancerMember https://appserv6.domain:7000 route=0
BalancerMember https://appserv7.domain:7000 route=1
ProxySet lbmethod=bybusyness nofailover=Off
stickysession=JSESSIONID|jsessionid
ProxyPass /clusterjsp balancer://appcluster-https/clus
I just was informed that this issue is already known:
https://issues.apache.org/bugzilla/show_bug.cgi?id=52402
I uploaded the proposed patch (from Florian Schröder) to
the bugid for this issue in patch format.
- Original Message -
From: "Zisis Lianas"
To: dev@httpd.apach
Just raised a bug for this issue:
https://issues.apache.org/bugzilla/show_bug.cgi?id=53420
httpd-2.2.x works correctly, error is only reproducable in 2.4.x.
- Original Message -
From: "Zisis Lianas"
To: dev@httpd.apache.org
Sent: Wednesday, May 9, 2012 11:00:36 PM
Subject: h
I noticed some different behaviour of SSLProxyCheckPeerCN in combination
with activated ProxyPreserveHost since httpd-2.4.3.
httpd-2.4.2 and httpd-2.2.22 seem to work 'correctly' (or vice versa).
When setting SSLProxyCheckPeerCN and ProxyPreserveHost to "on" in httpd-2.4.3,
i get an "AH02005: SSL
There seems to be some problems when trying to proxy "/" with
ProxyPass and mod_proxy_balancer.
See also:
https://issues.apache.org/bugzilla/show_bug.cgi?id=51982
https://issues.apache.org/bugzilla/show_bug.cgi?id=51489
I could reproduce both errors in httpd-2.4.3:
1) error 500 when configuring
uble-slashes
(httpd-2.4.3)
On Wed, Sep 5, 2012 at 6:08 PM, Zisis Lianas wrote:
> There seems to be some problems when trying to proxy "/" with
> ProxyPass and mod_proxy_balancer.
>
> See also:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=51982
> https://issues
nk this is a bug.
- Original Message -
From: "Tom Evans"
To: dev@httpd.apache.org
Sent: Thursday, September 6, 2012 4:40:18 PM
Subject: Re: Bug with "ProxyPass /" and mod_proxy_balancer + double-slashes
(httpd-2.4.3)
On Thu, Sep 6, 2012 at 12:42 PM, Zisis Lianas wrote
1, 2012 8:43:46 PM
Subject: Re: httpd 2.4.2 - mod_proxy id name not unique
Let me look into that... iirc, it was due to us wanting to
be able to persist data between restarts and using the time
as part of the id prevented that. But I could be mis-remembering.
On Apr 30, 2012, at 7:50 AM, Zisis
Tuesday, September 11, 2012 6:16:08 PM
Subject: Re: httpd 2.4.2 - mod_proxy id name not unique
I have to admit, I never really considered that case, but can't
you simply change the default location of the slotmem on one?
On Sep 11, 2012, at 10:01 AM, Zisis Lianas wrote:
> Hi Jim,
&g
: Wednesday, September 12, 2012 2:28:07 PM
Subject: Re: httpd 2.4.2 - mod_proxy id name not unique
Yes, that's the reason why the location of the file can be
user selectable. There's no need to adjust the name when you
can adjust the location/path.
On Sep 12, 2012, at 7:00 AM, Zisis Lian
12, 2012 at 8:40 AM, Zisis Lianas wrote:
> That's right, but on shared filesystems, "DefaultRuntimeDir"
> (logs/) and the non-unique shm-filenames state a problem.
Clarification: Do you want multiple web server instances to share the
same runtime directory without collisions of
12 3:45:44 PM
Subject: Re: httpd 2.4.2 - mod_proxy id name not unique
On Wed, Sep 12, 2012 at 9:31 AM, Zisis Lianas wrote:
> That's right, Jeff, that's exactly what I want.
>
> For other directives we never had collisions with a shared
> runtime directory (2.0 and 2.2), s
-- Original Message -
From: "Jim Jagielski"
To: dev@httpd.apache.org
Sent: Thursday, September 13, 2012 6:54:36 PM
Subject: Re: Bug with "ProxyPass /" and mod_proxy_balancer + double-slashes
(httpd-2.4.3)
On Sep 6, 2012, at 11:07 AM, Zisis Lianas wrote:
> Tom, thanks fo
- Original Message -
> From: "Jim Jagielski"
> To: dev@httpd.apache.org
> Sent: Thursday, September 13, 2012 8:59:27 PM
> Subject: Re: Bug with "ProxyPass /" and mod_proxy_balancer + double-slashes
> (httpd-2.4.3)
>
>
>
> So in the case it is correctly adjusting the backend URL Locati
- Original Message -
> Can you forward over your exact config again?
>
e.g.:
ProxyPreserveHost Off
BalancerMember http://backend01:5080 route=0
BalancerMember http://backend02:5080 route=2
BalancerMember http://backend01:5180 route=1
BalancerMember http://backend02:518
- Original Message -
> Try
>
> ProxyPreserveHost Off
>
>
>BalancerMember http://backend01:5080/ route=0
>BalancerMember http://backend02:5080/ route=2
>BalancerMember http://backend01:5180/ route=1
>BalancerMember http://backend02:5180/ route=3
>ProxySet lbmethod=bybu
It's always annoying after building an httpd-2.4 to see the AH01177 error
message when doing a quick start-check with "apachectl start":
[Fri Nov 16 16:29:19.093450 2012] [proxy_balancer:emerg] [pid 15902:tid
47671748469040] AH01177: Failed to lookup provider 'shm' for 'slotmem': is
mod_slotmem_s
Hi Pravesh,
this is the expected behaviour of SSLProxyCheckPeerCN. When
set to "on" (default), the certificate CN of the backend server
has to match the configured BalancerMember's name.
In your case, your BalancerMember seems to be "https://15.146.153.101/";
(so the name is "15.146.153.101"), wh
27 matches
Mail list logo
