net/http: add Pattern field in Request to return matched pattern info

[sillydong]

Fixes #66405

[gopherbot]

This PR (HEAD: 6cec642) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/574997.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Gopher Robot:

Patch Set 1:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: e68048d) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/574997.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Zhidong Chen:

Patch Set 1:

(2 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Damien Neil:

Patch Set 2: Hold+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Zhidong Chen:

Patch Set 2:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Damien Neil:

Patch Set 2:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: ac8c2d9) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/574997.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

This PR (HEAD: 1439e2f) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/574997.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Damien Neil:

Patch Set 4: Hold+1

(3 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: d3c9191) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/574997.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Zhidong Chen:

Patch Set 4:

(3 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 2eecc0a) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/574997.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Zhidong Chen:

Patch Set 5:

(2 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Jonathan Amsterdam:

Patch Set 6: Code-Review+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Jonathan Amsterdam:

Patch Set 6: Code-Review+2

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Jonathan Amsterdam:

Patch Set 6: Code-Review+1 Commit-Queue+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 6:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-05-15T21:11:43Z","revision":"b5998842000a6b37c9707ec65c94e341b80b7347"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Jonathan Amsterdam:

Patch Set 6:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Jonathan Amsterdam:

Patch Set 6: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 6:

This CL has failed the run. Reason:

Tryjob golang/try/gotip-linux-amd64 has failed with summary (view all results):

---

FAILURE

• go on master (change 574997)

Tests failed. See all test results.

Error: shard 4: failed to run "go tool dist test -json": exit status 1

Links:

• shard 4 build page
• shard 4 test results
• shard 4 "go tool dist test -json" (combined output)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 6: LUCI-TryBot-Result-1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Damien Neil:

Patch Set 6: -Hold Code-Review+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Jonathan Amsterdam:

Patch Set 6:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 264b3ca) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/574997.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Zhidong Chen:

Patch Set 7:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Damien Neil:

Patch Set 7: Code-Review+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 611e04d) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/574997.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Zhidong Chen:

Patch Set 7:

(2 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Damien Neil:

Patch Set 8: Code-Review+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Jonathan Amsterdam:

Patch Set 8: Code-Review+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Zhidong Chen:

Patch Set 8:

(3 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: c6e3274) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/574997.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Jonathan Amsterdam:

Patch Set 9: Code-Review+1 Commit-Queue+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 9:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-05-16T16:36:36Z","revision":"6545b6c99e95835d1b70128c221c91c1d2068a6b"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Damien Neil:

Patch Set 9: Auto-Submit+1 Code-Review+2

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Jonathan Amsterdam:

Patch Set 9: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 9:

This CL has failed the run. Reason:

Tryjob golang/try/x_tools-gotip-linux-amd64 has failed with summary (view all results):

---

FAILURE

• go on master (change 574997)
• tools on master (commit b92578a)

Error:

failed to run "test golang.org/x/tools module": exit status 1
failed to run "test golang.org/x/tools/gopls module": exit status 1

Links:

• "test golang.org/x/tools module" (combined output)
• "test golang.org/x/tools/gopls module" (combined output)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 9: LUCI-TryBot-Result-1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Jonathan Amsterdam:

Patch Set 9:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Damien Neil:

Patch Set 10: Code-Review+2 Commit-Queue+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 10:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-05-16T16:47:14Z","revision":"29e3205c20865b89a3c33e819386f214899a9e10"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Damien Neil:

Patch Set 10: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 10:

This CL has passed the run

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 10: LUCI-TryBot-Result+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Jonathan Amsterdam:

Patch Set 10: Code-Review+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574997.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR is being closed because golang.org/cl/574997 has been merged.