Today an article on a somewhat “technical” topic, which certainly does not interest everyone: In the context of my “correct” work I have to read out the HTTP header, which websites send for certain requests. For example, you can find out if a 404 error page from a web page actually sends a 404 status code, or maybe it only reports an error, but actually, sends a status code 200 OK.
So far, I have always used online services that are found under the term “Websniffer” or the like on the net. But you can do it easily with onboard resources from OS X, by using the terminal.
For example, if I want to query which headers the domain www.sir-apfelot.de reports, I enter this command in the terminal:
curl —HEAD https://docrazytricks.com
This works very well for me, but there are sometimes problems who the server does not understand the HEAD command and then sends no headers to curl. In this case you can also output the complete output when the page is called up with the verbose command “-v”. At the top then appear the things that interest us. But do not be surprised, you get the complete source code of the page displayed in the terminal, which can be here and there a lot of letter salad.
The correct command for this “complete edition” is:
curl –v https://docrazytricks.com