Add RFC 7240 to the specifications list

[LiviaMedeiros]

Description

Add RFC 7240 to the known specs list.

Motivation

This RFC is referenced as spec-urls in related pages: Prefer, Preference-Applied, but shows up as Unknown specification.

[github-actions]

Preview URLs

• /en-US/docs/Web/HTTP/Reference/Resources_and_specifications

Flaws (3)

URL: /en-US/docs/Web/HTTP/Reference/Resources_and_specifications
Title: HTTP resources and specifications
Flaw count: 3

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

[wbamberg]

I've got nothing against this change, but it won't fix:

This RFC is referenced as spec-urls in related pages: Prefer, Preference-Applied, but shows up as Unknown specification.

This comes out of the {{Specifications}} macro, which IIRC at least used to use the https://www.npmjs.com/package/browser-specs package to look up the spec name from its URL. It looks like RFC 7240 is not included in https://github.com/w3c/browser-specs/blob/main/specs.json, perhaps we could file an issue to request it?

(that's assuming {{Specifications}} does still use browser-specs. I don't know where the code for it is any more).

[wbamberg]

I filed w3c/browser-specs#2282, let's see what happens :).

[LiviaMedeiros]

Thanks!

If this relies on browser-specs, I'm not sure what's the best way to solve this. Prefer and Preference-Applied are not really related to browsers so there's a chance that w3c/browser-specs#2282 would be wontfix'd. But let's see.

Edit: nvm, w3c/browser-specs#2283 got merged. 🎉

[wbamberg]

Thanks!

If this relies on browser-specs, I'm not sure what's the best way to solve this. Prefer and Preference-Applied are not really related to browsers so there's a chance that w3c/browser-specs#2282 would be wontfix'd. But let's see.

Edit: nvm, w3c/browser-specs#2283 got merged. 🎉

🎉 I don't know how long it will take for MDN to pick up a new version of browser-specs, but when it does we can see if that fixes this issue.