Handling of fragment identifiers in redirected URLs
draft-bos-http-redirect-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Bert Bos | ||
| Last updated | 1999-07-19 | ||
| 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 HTTP 1.1 specification describes how a server can answer a request with a redirection, instructing the client to get the resource from a different URL. It doesn't explain what to do with any fragment identifier that might have been on the original URL, and this omission has resulted in different clients handling fragments in different ways. This draft gives rules towards a more consistent handling by future HTTP clients.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)