Found 1 record.

Status: Held for Document Update (1)

RFC 1866, "Hypertext Markup Language - 2.0", November 1995

Note: This RFC has been obsoleted by RFC 2854

Errata ID: 8572
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Ulrich Windl
Date Reported: 2025-09-12
Held for Document Update by: Andy Newton
Date Held: 2025-11-01

Section 8.2.2 says:

To process a form whose action URL is an HTTP URL and whose method is
`GET', the user agent starts with the action URI and appends a `?'
and the form data set (...)

It should say:

To process a form whose action URL is an HTTP URL and whose method is
`GET', the user agent adds the form data set to the [query of] action URI.

Notes:

I think the original authors had in mind to "add" the form data set to the action URI, but as specified it "replaces" any existing query parameters.
Maybe the authors focused on the syntax of specifying the query part more than on the aspect of how to add query parameters semantically.
Probably 30 years ago nobody had in mind that the action URI could be a parameter-driven CGI script like http://server.domain.org/example/api?fn=10&um=1 where the "fn" parameter specifies the action to take (and other parameters specify further details).
Having to add hidden form fields just to carry parameters to the action URL seems ugly today.
I'm aware that this change will cause incompatibilities also affecting https://www.w3.org/TR/html401/interact/forms.html#h-17.13.3.4, but if the form action is an URI it should be a complete URI. Section 8.1.1 also states " ACTION specifies the action URI for the form.". It does not specify that the query part might be ignored.
At least some clarification should be added.
See also https://stackoverflow.com/q/1116019/6607497

Report New Errata