>>
>>
>>
>>
>> -Original Message-----
>> From: Barry Chesterman [mailto:barrychester...@gmail.com]
>> Sent: Friday, 13 April 2012 1:29 AM
>> To: cfaussie@googlegroups.com
>> Subject: Re: [cfaussie] Re: Manipulating CFHTTP Source IP
>&
.com]
> Sent: Friday, 13 April 2012 1:29 AM
> To: cfaussie@googlegroups.com
> Subject: Re: [cfaussie] Re: Manipulating CFHTTP Source IP
>
> x-forwarded-for is really only an additional header stapled onto an
> http request and I would have thought any external system accepting a
> limited n
For that to happen it would need to happen within the firewall or after the
firewall
-Original Message-
From: Barry Chesterman [mailto:barrychester...@gmail.com]
Sent: Friday, 13 April 2012 1:29 AM
To: cfaussie@googlegroups.com
Subject: Re: [cfaussie] Re: Manipulating CFHTTP Source IP
x
x-forwarded-for is really only an additional header stapled onto an
http request and I would have thought any external system accepting a
limited number of requests from a specific IP wouldn't even be looking
at x-forwarded-for for decision making (although it depends how the
logic is written at th
Phil
All your outgoing connections will go out via the IP address configured as
your firewalls IP address. This means any web services you are connecting
to, no matter what you do programmatically will all come from the same IP
address
-Original Message-
From: Phil Rasmussen [mailto:ara.
