We needed a new approach to solve this issue, and so the Postman engineering team got to work to find a breakthrough. In our journey back to the web, the CORS limitation was a fundamental, ongoing issue that hindered our ability to bring an amazing API developer experience to the browser. In the early days of Postman, these challenges with CORS while working with APIs in the browser quickly pushed Postman from the web to the desktop, resulting in the Windows and Mac versions of the Postman app that developers depend on today. This feature protects website users from malicious activity, but it is also something that negatively impacts one of the core capabilities of web APIs: the accessing of data, content, media, and algorithms across a variety of domains.Īs a developer, if you’ve had the chance to work with many APIs using JavaScript in the browser, then you have no doubt encountered challenges using cross-origin resource sharing (CORS). Leading browsers like Chrome and Firefox restrict how data is exchanged between different internet domains, limiting requests to the domain you have loaded in the address bar. Modern browsers are great for humans surfing websites, but they have limitations when it comes to pulling data from APIs across many different domains. The limitation of cross-origin resource sharing (CORS) in browsers We needed to overcome a fundamental limitation of browser architectures to truly bring the Postman experience to the web.
(We encourage you to read the launch blog post here.)īut bringing Postman to the web wasn’t as easy as simply building a browser-based UI. Today we announced a new beta version of Postman that we’ve been working on to address a wide range of requests from our fantastic user community: Postman on the web.
0 kommentar(er)
