ISSUE-289 (includeOriginalHeaders): Should CT proxies send X-Device-* headers after having determined the content is not mobile-optimized? [Guidelines for Web Content Transformation Proxies] from Mobile Web Best Practices Working Group Issue Tracker on 2009-03-10 (public-bpwg@w3.org from March 2009)

From: Mobile Web Best Practices Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 10 Mar 2009 11:00:19 -0400 (EDT)
To: public-bpwg@w3.org
Message-Id: <20090310150019.7857F7F460@otto.w3.org>

ISSUE-289 (includeOriginalHeaders): Should CT proxies send X-Device-* headers after having determined the content is not mobile-optimized? [Guidelines for Web Content Transformation Proxies]

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

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

If we mandate sending X-Device-* headers, this should be done with a mention they could get deprecated in the future (per ACTION-897 and ACTION-912).

But is there any point in having the headers sent? If the content is mobile-optimized, the CT proxy shouldn't transform it anyway, and if it isn't, it's unlikely the CT provider will do anything with these additional headers.

Received on Tuesday, 10 March 2009 15:00:28 UTC