- From: Amos Jeffries <squid3@treenet.co.nz>
- Date: Fri, 18 Jan 2013 22:18:03 +1300
- To: ietf-http-wg@w3.org
On 17/01/2013 12:25 p.m., Mark Nottingham wrote: > On 17/01/2013, at 10:23 AM, Nico Williams wrote: > >> On Wed, Jan 16, 2013 at 5:10 PM, Mark Nottingham wrote: >>> On 17/01/2013, at 9:45 AM, James M Snell <jasnell@gmail.com> wrote: >>> Dates in HTTP are explicitly in UTC (we just call it "GMT"), so the timezone data isn't helping (and may be hurting). >> TZ should be in a separate header then. It helps the server to know >> what TZ a user is in. > That's been discussed quite a bit already, and is separable from HTTP/2. For starters, the Date header is seldom sent in requests... Indeed. The main use of dates in HTTP/1 is communication about objects stored on the server and the client has no visible use for information about server timezone. The main use-cases I hear presented for transferring TZ information are content personalization or user tracking by the server. In both cases it ought to be an optional header which can be a) suppressed by users not wanting to distribute such information about themselves and b) used by the serve in Vary: lists to signal the content customization. Amos
Received on Friday, 18 January 2013 09:18:39 UTC