Search RFCs

RFC Editor

Found 3 records.

Status:Verified (2)

RFC 1738, "Uniform Resource Locators (URL)", December 1994

Note: This RFC has been obsoleted byRFC 4248, RFC 4266

Note: This RFC has been updated byRFC 1808, RFC 2368, RFC 2396, RFC 3986, RFC 6196, RFC 6270, RFC 8089

Errata ID:5118
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: literal slash needed in gopher BNF
Date Reported: 2017-09-15
Verifier Name: Alexey Melnikov
Date Verified: 2017-09-21

Section 5. says:

gopherurl      = "gopher://" hostport [ / [ gtype [ selector                 [ "%09" search [ "%09" gopher+_string ] ] ] ] ]

It should say:

gopherurl      = "gopher://" hostport [ "/" [ gtype [ selector                 [ "%09" search [ "%09" gopher+_string ] ] ] ] ]

Notes:

The slash after the first square bracket open should be quoted because it is a literal slash, as evidenced in the example in section 3.4.1:

3.4.1. Gopher URL syntax

gopher://<host>:<port>/<gopher-path>

Errata ID:4917
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Stephan Casas
Date Reported: 2017-01-26
Verifier Name: John Scudder
Date Verified: 2024-01-15

Section 2.2 says:

the chararacter which has that octet as its code within the US-ASCII[20] coded character set.

It should say:

the character which has that octet as its code within the US-ASCII[20] coded character set.

Notes:

The word "character" is misspelled as "chararacter."

Status:Rejected (1)

RFC 1738, "Uniform Resource Locators (URL)", December 1994

Note: This RFC has been obsoleted byRFC 4248, RFC 4266

Note: This RFC has been updated byRFC 1808, RFC 2368, RFC 2396, RFC 3986, RFC 6196, RFC 6270, RFC 8089

Errata ID:2845
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Mykyta Yevstifeyev
Date Reported: 2011-06-26
Rejected by: Peter Saint-Andre
Date Rejected: 2011-06-27

Section 5 says:

scheme         = 1*[ lowalpha | digit | "+" | "-" | "." ][ . . . ]hostname       = *[ domainlabel "." ] toplabeldomainlabel    = alphadigit | alphadigit *[ alphadigit | "-" ] alphadigittoplabel       = alpha | alpha *[ alphadigit | "-" ] alphadigit[ . . . ]user           = *[ uchar | ";" | "?" | "&" | "=" ]password       = *[ uchar | ";" | "?" | "&" | "=" ][ . . . ]fpath          = fsegment *[ "/" fsegment ]fsegment       = *[ uchar | "?" | ":" | "@" | "&" | "=" ][ . . . ]hpath          = hsegment *[ "/" hsegment ]hsegment       = *[ uchar | ";" | ":" | "@" | "&" | "=" ]search         = *[ uchar | ";" | ":" | "@" | "&" | "=" ][ . . . ]group          = alpha *[ alpha | digit | "-" | "." | "+" | "_" ]article        = 1*[ uchar | ";" | "/" | "?" | ":" | "&" | "=" ] "@" host[ . . . ]ppath          = psegment *[ "/" psegment ]psegment       = *[ uchar | "?" | ":" | "@" | "&" | "=" ]fieldspec      = ";" fieldname "=" fieldvaluefieldname      = *[ uchar | "?" | ":" | "@" | "&" ]fieldvalue     = *[ uchar | "?" | ":" | "@" | "&" ]

It should say:

scheme         = 1*( lowalpha | digit | "+" | "-" | "." )[ . . . ]hostname       = *( domainlabel "." ) toplabeldomainlabel    = alphadigit | alphadigit *( alphadigit | "-" ) alphadigittoplabel       = alpha | alpha *( alphadigit | "-" ) alphadigit[ . . . ]user           = *( uchar | ";" | "?" | "&" | "=" )password       = *( uchar | ";" | "?" | "&" | "=" )[ . . . ]fpath          = fsegment *( "/" fsegment )fsegment       = *( uchar | "?" | ":" | "@" | "&" | "=" )[ . . . ]hpath          = hsegment *( "/" hsegment )hsegment       = *( uchar | ";" | ":" | "@" | "&" | "=" )search         = *( uchar | ";" | ":" | "@" | "&" | "=" )[ . . . ]group          = alpha *( alpha | digit | "-" | "." | "+" | "_" )article        = 1*( uchar | ";" | "/" | "?" | ":" | "&" | "=" ) "@" host[ . . . ]ppath          = psegment *( "/" psegment )psegment       = *( uchar | "?" | ":" | "@" | "&" | "=" )fieldspec      = ";" fieldname "=" fieldvaluefieldname      = *( uchar | "?" | ":" | "@" | "&" )fieldvalue     = *( uchar | "?" | ":" | "@" | "&" )

Notes:

Given this is BNF of RFC 822 construction <n>*<m>[element] is incorrect, as RFC 822 defines:

> 2.5. [RULE]: OPTIONAL
>
> Square brackets enclose optional elements; "[foo bar]" is
> equivalent to "*1(foo bar)".

and therefore [] construction is illegal in the aforementioned one. My proposal is to replace all occurrences of [] construction where they are used in the meaning of () with the legal-as-per-822 one.
--VERIFIER NOTES--
This specification does not use the BNF syntax from RFC 822. Please refer
to the first paragraph of Section 5:

###

This is a BNF-like description of the Uniform Resource Locator
syntax, using the conventions of RFC822, except that "|" is used to
designate alternatives, and brackets [] are used around optional or
repeated elements. Briefly, literals are quoted with "", optional
elements are enclosed in [brackets], and elements may be preceded
with <n>* to designate n or more repetitions of the following
element; n defaults to 0.

###

The definitions follow the syntax used in this document. Thus
the report is incorrect.

Report New Errata