Re: [squid-users] Handling GeoIP specific content

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Unfortunately, that wouldn't help in this case... Even if we send
domestic traffic directly to the servers, any traffic that (rightly so
based on DNS/Geo separation) ends up on the euro based caches, would
only appear to originate from the country they are based in. We lose
granularity at the country level...

I think we're gonna try to play around with follow-x-forwarded and
apache to see if we can parse based on that.

thanx,
sascha =)

On Dec 3, 2007, at 1:10 PM, John Moylan wrote:

> Some sites use dynamic DNS based on lookups to something like
> Maxmind or Quova.
>
> J
>
> On Dec 3, 2007 6:02 PM, Sascha Linn <slinn@hoodiny.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi all,
>>
>> I'm sure someone has to have dealt with this... but I cal only find
>> one hit in the archives relating to dealing with GeoIP specific
>> content. And it's over a year old (a patch for 2.5 that appends a
>> header to the request.)
>>
>> Basically, we want to have a reverse proxy in Europe to offload some
>> of our traffic (servers in the US.) However, some of the content on
>> the site is GeoIP specific (ie. users in Spain see one thing, those
>> in
>> France another.) What's the best way to deal with this?
>>
>> thanx,
>> sascha =)
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.7 (Darwin)
>>
>> iD8DBQFHVES7NIqNkZp0KoQRAjk5AJ0SHQgnch1U5bPNrr8zUHEXwwrrqgCgzeYW
>> C84xqyPoNiW2q7tcE4EK8zA=
>> =9Lab
>> -----END PGP SIGNATURE-----
>>

Sascha Linn | HOODINY

slinn@hoodiny.com
o: 1.305.722.7000 x.415
m: 1.213.631.0879

1960 e. grand ave., suite 240
el segundo, ca 90245
www.hoodiny.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFHVHZCNIqNkZp0KoQRAhB4AJ9IZkvHHSb5mU4jkhFMPRxPXO35BgCeK6mi
9ajA+5d07QIf1cUY5iQRVS4=
=+1Ss
-----END PGP SIGNATURE-----
Received on Mon Dec 03 2007 - 14:33:58 MST