Edit - Unix & Linux Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

1

Although many webservers will Postelianly accept that, the lines of an HTTP request header (or response header also) should end with CRLF not just LF, and there should be only one empty line following the header not two. Also header names may vary in capitalization, which gawk can handle easily with IGNORECASE=1 .

dave_thompson_085
– dave_thompson_085

2025-05-16 22:45:27 +00:00
Commented May 16 at 22:45
Thanks, didn't know that! Added both changes.

wobtax
– wobtax

2025-05-16 23:56:48 +00:00
Commented May 16 at 23:56

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »