Privacy and HTTP intermediaries

The issue of logging HTTP requests has come up in a discussion in another working group.

The goal is not just to prevent someone from learning that a certain person requested a certain resource, but to protect the identity of the resource.  That is, the very existence of the resource is a secret.

I understand that with CONNECT an intermediary only really knows that a particular server has been contacted, but what about unsecured HTTP?  Does the value of the Cache-Control header have any bearing on whether something is logged?

What sort of logging does an HTTP intermediary typically do?

--Martin

Received on Tuesday, 3 May 2011 01:10:42 UTC