Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: mod_proxy: maximum hostname length for workers
From: Jim Jagielski <jim@jaguNET.com>
In-Reply-To: 
 <CAPV0b04c5TDNf_5TbBS3XK4EfiMNaXHyAs5b7gK6NbfpwC9COw@mail.gmail.com>
Date: Fri, 8 Nov 2013 09:35:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <686FD502-3302-4391-BCCE-A7707412A96D@jaguNET.com>
References: 
 <CAPV0b04c5TDNf_5TbBS3XK4EfiMNaXHyAs5b7gK6NbfpwC9COw@mail.gmail.com>
To: dev@httpd.apache.org

Yeah, it's basically for performance and storage reasons (since those
strings are stored in shm)... Nowadays I don't think shm is such an
expensive commodity, though I can imagine some setups where the
default sizes allowed by the kernel could be kinda small.

I'd be +1 in adjusting all of those fields bigger, but I'm guessing
that constitutes an API change for proxy...

On Nov 8, 2013, at 5:17 AM, Thomas Eckert <thomas.r.w.eckert@gmail.com> =
wrote:

> I'm looking at an issue with this log message
>=20
>   AH00526: Syntax error on line 6 of myconfig.conf: BalancerMember =
worker hostname =
(aaaaaaaa-bbbb-cccc-dd-eee-ffffffffff.us-east-1.elb.amazonaws.com) too =
long
>=20
> with the root cause being (modules/proxy/mod_proxy.h)
>=20
>   #define PROXY_WORKER_MAX_HOSTNAME_SIZE  64
>=20
> and I'm wondering why this is. I did not see any comments on why there =
is this limit, so I assume it's for performance reasons.
>=20
> Also, I'm wondering what the implications (if any) of altering this =
limit are.