Parsing URLs for Fun and Profit
draft-abarth-url-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Adam Barth | ||
| Last updated | 2011-04-23 | ||
| 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
This document contains a precise specification of how browsers process URLs. The behavior specified in this document might or might not match any particular browser, but browsers might be well-served by adopting the behavior defined herein.Editorial Note (To be removed by RFC Editor) If you have suggestions for improving this document, please send email to <mailto:public-iri@w3.org>. Further Working Group information is available from <https://tools.ietf.org/wg/iri/>.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)