News for hackers. Stuff that matters.

A comment on /story/36179850. Parent comment

Re: by madacol on Saturday June 03, 2023 @08:55PM (#36181977)
cool!

nc google.com 80

    HEAD / HTTP/1.1

    HTTP/1.1 200 OK
    ...
Hint: write `HEAD / HTTP/1.1` and hit twice {ENTER}
[ Parent | on HN ]
Re: by imoverclocked on Saturday June 03, 2023 @09:57PM (#36182316)
“curl -v url” saves a lot of typing while also supporting https/vhosts/etc while still showing all of the communication and other debug info.
[ Parent | on HN ]
Re: by Sophira on Sunday June 04, 2023 @08:37AM (#36185148)
I'm actually a little surprised that worked; one of the major differences between HTTP/1.0 and HTTP/1.1 is that all HTTP/1.1 requests MUST include a Host HTTP header, so technically a HTTP/1.1 request without such a header is malformed.
[ Parent | on HN ]
Re: by ttfkam on Sunday June 04, 2023 @11:14AM (#36186256)
Web servers have always had to be written for the web clients that existed, not how they should have existed.

Sadly, a 100%-compliant web server (or client for that matter) would be greatly hobbled as to who it could communicate with on the real web. Although I do think the situation is far better now than it was 20 years ago.

[ Parent | on HN ]