The last item ( console.log output) is the another compelling reason why I keep going back to Postman Console. Error logs from test or pre-request scripts.What proxy and certificates were used during making the request.The exact response sent by the server before it is processed by Postman.The actual request that was sent, including all underlying request headers, etc. ![]() At times, knowing exactly what these headers looked like helps me debug server issues faster than if I had used any other tool.Ĭurrently Console also logs the following information: Beyond the request headers one provides, Postman automatically sends additional useful headers that your server needs, and it is beneficial to know about them. This saves me a lot of time while debugging the request that was sent.Īnother notable feature is the ability to inspect the entire list of headers that was sent when I request using Postman. The most useful information, for me personally, is that every request is logged in the console in its raw form, replacing all the variables that I have used in a request. It simply looks “geeky” that way! Ok, what else? As long as the console window is open, all your API activities will be logged here for you to see what’s going on under the hood. The keyboard shortcut to fire up the console is cmd + alt + c ( ctrl + alt + c on Windows).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |