To enable the Interceptor extension, click on the toggle icon inside the navbar. The Interceptor modifies requests sent from Postman on the fly without you having to do any extra work. You can also modify headers like Date, User-Agent etc. If you have Postman installed already, then you might have to re-enable it from the top right menu. The permission is used to communicate to the Interceptor extension as well as the Postman website (more on this in another post). Now you can log into a website and Postman will use your login credentials to make your API calls just like the legacy app! This allows you to test APIs which use cookie-based authentication schemes. Chrome apps, extensions and web pages can communicate between each other using Chrome’s message passing API. Using the messaging passing API, the Postman app can route requests through an extension which has access to browser cookies. This is achieved using the new Postman Interceptor extension. With the release of the 0.9.6 version, you can now access cookies as well as restricted headers. Using a proxy did let you get around these issues, but was not exactly an elegant solution. (Well, Postman is being used to test entire websites and SOAP APIs too!) While one can argue about why cookies are being used in REST APIs, or why XMLHttpRequest restricts certain headers in an app, the issue does affect developers who want to test their APIs. The second was to send headers restricted by the XMLHttpRequest specification. First was the inability to use browser cookies. Ever since the packaged app release, there have been a couple of restrictions that have held back some developers from upgrading.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |