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).
If an API or API test is not behaving as you expect, this would be the place where you will go to deep dive while debugging the same. Postman Console is analogous to a browser’s version of the developer console, except that it’s tuned for API development. Here’s the summary of what the new Console in Postman is all about: Hence, we built one that is easier to use. The console (albeit extremely powerful) was an overwhelming source of information to find the simplest and obvious things associated with daily use of Postman. One of the scariest things that we had to do (and recommend others to do as well) was to open up the underlying Chrome DevTools for simple things as inspecting your requests. This new feature is so exciting that Vignesh (the one who started working on it) literally renamed himself to “console”! With the release of Postman v4.5 for Mac, we introduced a new feature called the Postman Console. If this topic interests you, check our recent blog posts with updates about the new Postman Console pane and powerful debugging.
0 kommentar(er)
