Handling of fragment identifiers in redirected URLs
draft-bos-http-redirect-00

Document Type Expired Internet-Draft (individual)
Author Bert Bos 
Last updated 1999-07-19
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-bos-http-redirect-00.txt

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

Bert Bos (bert@w3.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)