Colm MacCárthaigh wrote:
I don't think permitting hostname/number is a good idea, because a
hostname can map to multiple IPs, and it gets confusing, it's
non-standard :-) Right now the code just does a single lookup, and uses
that - so where there are multiple A/ records we'll have
On Wed, Apr 1, 2009 at 12:45 AM, William A. Rowe, Jr.
wr...@rowe-clan.netwrote:
I have essentially finished mod_remoteip at this point and am looking
to find out the interest level of adopting this as a core module into
trunk (modules/metadata/ appears to be the most appropriate target)?
+1
Graham Leggett wrote:
William A. Rowe, Jr. wrote:
I have essentially finished mod_remoteip at this point and am looking
to find out the interest level of adopting this as a core module into
trunk (modules/metadata/ appears to be the most appropriate target)?
+1.
That's two of us; I'm
William A. Rowe, Jr. wrote:
I have essentially finished mod_remoteip at this point and am looking
to find out the interest level of adopting this as a core module into
trunk (modules/metadata/ appears to be the most appropriate target)?
+1.
I had to code up a similar feature recently in
Graham Leggett wrote:
(Having not yet had a chance to look at the code) How is the possibility
of multiple IPs in the same header handled, eg:
X-Fowarded-For: 10.2.3.4, 10.11.12.13
I think you'll find your question is answered in the README I referenced.
It's handled fine. The interesting
I have essentially finished mod_remoteip at this point and am looking
to find out the interest level of adopting this as a core module into
trunk (modules/metadata/ appears to be the most appropriate target)?
mod_remoteip can deal with 2 situations effortlessly, one is the
absolute
