mirror of
https://github.com/golang/go.git
synced 2026-08-02 20:44:20 +08:00
d90bf6d722
Implement MaxHeaderValueCount support for both the HTTP/1 and HTTP/2 server. This allows servers who want to support large headers such as SSO or OIDC cookies (and therefore has to set MaxHeaderBytes to a large value), to still limit the number of headers that they are willing to accept. Also added the usual note for linknamed symbols for net/textproto.readMIMEHeader, which seems to have been missed originally. Release note changes will be added directly in x/website. For #79936 Change-Id: I600ac6c492f64f9cfa2730836be64dc76a6a6964 Reviewed-on: https://go-review.googlesource.com/c/go/+/795460 Reviewed-by: Nicholas Husin <husin@google.com> Reviewed-by: Damien Neil <dneil@google.com> LUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Files in this directory are data for Go's API checker ("go tool api", in src/cmd/api).
Each file is a list of API features, one per line.
go1.txt (and similarly named files) are frozen once a version has been
shipped. Each file adds new lines but does not remove any.
except.txt lists features that may disappear without breaking true
compatibility.
Starting with go1.19.txt, each API feature line must end in "#nnnnn"
giving the GitHub issue number of the proposal issue that accepted
the new API. This helps with our end-of-cycle audit of new APIs.
The same requirement applies to next/* (described below), which will
become a go1.XX.txt for XX >= 19.
The next/ directory contains the only files intended to be mutated.
Each file in that directory contains a list of features that may be added
to the next release of Go. The files in this directory only affect the
warning output from the go api tool. Each file should be named
nnnnn.txt, after the issue number for the accepted proposal.
(The #nnnnn suffix must also appear at the end of each line in the file;
that will be preserved when next/*.txt is concatenated into go1.XX.txt.)
When you add a file to the api/next directory, you must add at least one file
under doc/next. See doc/README.md for details.