> I have not used google analytics, so I don't know. In theory, it > could/should still work. The original client ip is, afaik, included in > the http header "X-Forwarded-For". > It's pretty much as if the user uses a proxy server (i.e. a forward > proxy, not a reverse proxy) - how does google analytics deal with > that?
X-Forwarded-For is a hint for web servers. In apache, in example, page hits are always based on the connecting address, not on the X-Forwarded-For content. If the google staff did manage to handle it in code, well, fine. I don't think so, anyway. But have no proof either sides... > Plus, I think they use cookies for the actual tracking, those should > not be affected. But as I said, I have never used it, so I really > can't be sure. > > I used mod_proxy it in the past to include some snippets provided on a > site via plain html inside an https page. No kind of tracking was > necessary. Oh, well. Analytics is just a timed counter, after all. It should work anyway... > hth, Lutz > > On 6/19/06, Giampaolo Tomassoni <[EMAIL PROTECTED]> wrote: > > If this is done to fire a hit in google analytics, wouldn't > google report the ip address and country of the server instead of > the client's ones? > > > > giampaolo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
