Skip to content

Conversation

@joshkgarber
Copy link
Contributor

Description

In the description of the example HTTP message a reference is made to an empty line which doesn't exist. Inserting the missing empty line in the example HTTP message shows how the empty line properly terminates the header section as described in the page content.

Motivation

The non-existence of the empty line should be fixed so that users are not confused by it being referred to, yet not being there. This contribution hopefully prevents such confusion.

Additional details

They empty line is mentioned in section 2.1 of RFC9112

I also considered adding "[ empty line ]" or "CRLF" as shown in the RFC but decided not to as a simple empty line is consistent with the next example directly after it, which contains a similar empty line.

Related issues and pull requests

N/A

Inserting the missing empty line in the example HTTP message  shows how the empty line properly terminates the header section as described in the page content.
@joshkgarber joshkgarber requested a review from a team as a code owner November 14, 2025 17:05
@joshkgarber joshkgarber requested review from bsmth and removed request for a team November 14, 2025 17:05
@github-actions github-actions bot added Content:HTTP HTTP docs size/xs [PR only] 0-5 LoC changed labels Nov 14, 2025
@github-actions
Copy link
Contributor

Preview URLs

Flaws (3)

URL: /en-US/docs/Web/HTTP/Guides/Session
Title: A typical HTTP session
Flaw count: 3

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

Copy link
Member

@bsmth bsmth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, let's add it here, thanks 👍🏻

@bsmth bsmth merged commit 5889fe9 into mdn:main Nov 17, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Content:HTTP HTTP docs size/xs [PR only] 0-5 LoC changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants