doc: updateSafeMethodsAndIdempotentMethods

[samuel871211]

Description

• Of the request methods defined by this specification, the GET, HEAD, OPTIONS, and TRACE methods are defined to be safe.
• Of the request methods defined by this specification, PUT, DELETE, and safe request methods are idempotent.

Motivation

Additional details

RFC9110 Safe Methods
RFC9110 Idempotent Methods

Related issues and pull requests

[github-actions]

Preview URLs

• /en-US/docs/Web/HTTP/Guides/Connection_management_in_HTTP_1.x

Flaws (3)

URL: /en-US/docs/Web/HTTP/Guides/Connection_management_in_HTTP_1.x
Title: Connection management in HTTP/1.x
Flaw count: 3

• unknown:
  • No generic content config found
  • no blog root
  • no blog root

(comment last updated: 2025-11-19 11:07:20)

[bsmth]

Thanks a lot for the suggestion. I think the important part on the glossary is that we're talking about common methods, and TRACE is lesser-used because people like to disable it for concerns that it leaks information about the server:

• https://portswigger.net/web-security/information-disclosure/exploiting#information-disclosure-due-to-insecure-configuration

For this reason, I think it's probably better to omit it on the glossary page

[bsmth]

Thank you!