Remove HTTP status 102 page

[OnkarRuikar]

Description

The PR is a result of the following conversation on Discord:

Onkar : Should we delete the Web/HTTP/Reference/Status/102 page?
It was deprecated in 2018 and is not being tracked in BCD. Also, no browser recognises it.

Ruth: Yes I think so - we can still list it here https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status with no link and prose to say it was deprecated (like 305/306)

More Info

I ran the following command for the deletion:

npm run content delete Web/HTTP/Reference/Status/102 en-US -- --redirect Web/HTTP/Reference/Status#102_processing

[github-actions]

Preview URLs (1 page)

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

External URLs (1)

URL: /en-US/docs/Web/HTTP/Reference/Status
Title: HTTP response status codes

• https://www.rfc-editor.org/info/rfc4918/ (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2026-09-01 04:57:36)

[hamishwillee]

FWIW I like the idea of having a section for deprecated status rather than just dropping them. But I think it probably should be thin as a list (perhaps with "not supported since 2018 or whatever") and you'd link to the top level list

[OnkarRuikar]

Just mirrored like what happened to the 305 and 306 statuses: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status#305_use_proxy

But I think it probably should be thin as a list (perhaps with "not supported since 2018 or whatever") and you'd link to the top level list

Maintaining status specific lists is hard. I think we actively got rid of them in the past. We have inline deprecation indicator badges to rely on.
There is nothing much on the the current 102 status page itself. Whatever it is I've moved it to this page now.