chore(http): Move Ogg guide, HTTP method fixes

[bsmth]

A couple of small fixes for HTTP section

Changes:

• Move Ogg guide into Media section
  • Some cleanup in Ogg guide
• Browser compat information about HTTP methods.
• Update a few links
  • Node docs
  • web.dev

[github-actions]

Preview URLs (9 pages)

• /en-US/docs/Web/HTML/Element/video
• /en-US/docs/Web/HTTP/CSP
• /en-US/docs/Web/HTTP/Cookies
• /en-US/docs/Web/HTTP/Methods/DELETE
• /en-US/docs/Web/HTTP/Methods/PATCH
• /en-US/docs/Web/HTTP/Methods/PUT
• /en-US/docs/Web/HTTP/Methods/TRACE
• /en-US/docs/Web/HTTP
• /en-US/docs/Web/Media/Formats/Configuring_servers_for_Ogg_media

External URLs (5)

URL: /en-US/docs/Web/HTTP/CSP
Title: Content Security Policy (CSP)

• https://web.dev/articles/strict-csp (1 time) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Web/HTTP/Cookies
Title: Using HTTP cookies

• https://api.rubyonrails.org/classes/ActionDispatch/Cookies.html (1 time) (Note! This may be a new URL 👀)
• https://docs.python.org/3/library/http.cookies.html (1 time) (Note! This may be a new URL 👀)
• https://nodejs.org/docs/latest-v19.x/api/http.html (1 time) (Note! This may be a new URL 👀)
• https://www.php.net/manual/en/function.setcookie.php (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2024-12-01 22:36:35)

[hamishwillee]

@bsmth All of these method updates "seem reasonable" - meaning I can't think of a case where a browser emits them except via a direct user API call to fetch or XHR or whatever. Nor where the response to a DELETE (or the others) is specially handled as a result of the original DELETE call. So in other words the browser doesn't really have any "DELTEE" implementation as such.

But I wouldn't have changed these without first working to get agreement and removal in BCD. Maybe you already did that? If not, can you kick it off?

[bsmth]

But I wouldn't have changed these without first working to get agreement and removal in BCD. Maybe you already did that? If not, can you kick it off?

Earlier in the year we discussed HTTP statuses and headers in BCD where support means "nothing breaks" -> the browser doesn't set them in requests and doesn't act on them in responses, but application-specific logic can be done using fetch(). I'll add this to the BCD call notes for this week to make sure this prose is okay, so thanks for flagging it 👍🏻

[hamishwillee]

Thanks @bsmth . Makes sense to me - merging.

Note #37026 (comment) - possible post-process activity