> 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 anal
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 dea
> Talking about apache: including external content on https sites via
> http can in many cases be done without triggering warnings, by making
> a directory on your https server a reverse proxy using mod_proxy.
If this is done to fire a hit in google analytics, wouldn't google report the
ip addres
On Mon, 19 Jun 2006 10:43:07 -0400, Giampaolo Tomassoni
<[EMAIL PROTECTED]> wrote:
Nah! Search engine don't access https and lazily browsing a site
wouldn't require an https link as well. Nobody would advocate http
support. But, again, when you enter an https there is a reason (a login
o
> > Switching back to http was an old habit: five years ago, when internet
> > bandwidth were really narrow and cpu power wasn't that high, it could
> > have made a difference. Today these are not anymore issues. I
> would try
> > to stress this fact and the security issues the http/https mi
