CARVIEW |
Select Language
HTTP/2 200
date: Wed, 08 Oct 2025 17:18:00 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=AIdIizMoUjntdMlsWDahuEhcCXXUHfdsJLetwGD.eEQ-1759943880-1.0.1.1-SxHKher.UAcCymb.ttdVVZVmvSLyARtJohfMfm9RZZkbe2i1XLzDI5moipzQEGDQTDrMmRzTH.1OBpwsUwCwFjbc4PKGUx75vNxM9gRnGXI; path=/; expires=Wed, 08-Oct-25 17:48:00 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98b74b7bcc09c1f7-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2718 » RFC Editor
Search RFCs
RFC 2718
Guidelines for new URL Schemes, November 1999
- File formats:
- Status:
- INFORMATIONAL
- Obsoleted by:
- RFC 4395
- Authors:
- L. Masinter
H. Alvestrand
D. Zigmond
R. Petke - Stream:
- IETF
- Source:
- urlreg (app)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2718
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2718
Abstract
This document provides guidelines for the definition of new URL schemes. This memo provides information for the Internet community.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us