ISSUE-260 (Client/Proxy black box): Do the guidelines address Client/Proxy solutions? [Content Transformation Guidelines]

ISSUE-260 (Client/Proxy black box): Do the guidelines address Client/Proxy solutions? [Content Transformation Guidelines]

http://www.w3.org/2005/MWI/BPWG/Group/track/issues/

Raised by: François Daoust
On product: Content Transformation Guidelines

Raised as an issue so that we don't forget to address this during the F2F in Sophia...

>From the point of view of a Content Provider, a Client/Proxy solution (such as Opera Mini) behaves like a black box, and as such should be regarded as a regular user agent.

But, even black holes do let information escape (at 1000 bytes per second according to last calculations, or so I read, but I'm stepping out of topic here), and so the black box may "leak".

Typically, the Proxy part may still behave (at least a bit) as a non-transparent proxy, and for instance may hide the originating IP address of the client. In such a case, the guidelines may partially apply (e.g. add an X-Forwarded-For HTTP header).

Jo suggests to explain this in an Appendix.