igrigorik
commented
9 years ago @mnot I'd still like to propose that we come up with a general purpose header to indicate a "delayed request". Some use cases:
- UA delays delivery of a Beacon due to
- e.g. offline, retrying, batching. - ServiceWorker intercepts requests, logs them, and then forwards them to the server later - e.g. once back online, or due to some internal buffering / aggregation logic, etc.
a) We could extend Age, which is currently defined as a response header?
b) We can come up with a new name - e.g. Request-Age, or some such?
Having a generic, well-defined header would allow reasonable interop between different servers, analytics vendors, etc., for processing delayed requests.
mnot
We created a new HTTP header for Beacon-Age. We should consider registering it using http://tools.ietf.org/html/rfc3864#section-4.3
If we want a permanent status, we will need to define the ABNF, etc.; see http://httpwg.github.io/specs/rfc7231.html#considerations.for.new.header.fields.
This is a not blocker for CR.