Geolocation Header for HTTP over a Secure Context
draft-luisbarguno-geolocation-header-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Luis Barguñó Jané | ||
| Last updated | 2018-04-19 (Latest revision 2017-08-08) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Geolocation header introduces a mechanism to send a device location over an HTTP Secure Context from a user agent to a server. The Geolocation-Request header is used by a server to inform the user agent when a Geolocation header is requested to be sent. This mechanism, through persistent Geolocation-Requests, provides a single-roundtrip solution to obtain location-aware responses for location-aware services, as oposed to existing JS-based Geolocation API that require two round trips.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)