Chrome will honor untrusted certificates you have added to your OS as trusted (hence this behavior) and there is also a way to whitelist certificates on a case to case basis by opening the link in Chrome and clicking "proceed" in at the "Your connection is not secure" (which is why you are seeing this behavior). Postman for Chrome apps rely on Chrome to send and receive requests and Postman app has no control over SSL certificate verification performed by Chrome as part of sending the request. The original comment is related to working with untrusted SSL certificates in Postman for Chrome. where do I go from I'm condensing this discussion and adding our thoughts here. I granted "everyone" full control rights to the directory, and then added the cert to postman. and dropped it in to a new folder in the root of my hard drive. I took my "cer" file (that I had to extract using firefox as I couldn't find any option in either chrome or postman to extract this). Which I assume is related to the first error and thus the root of my problem.Īs Postman seems to not have access to a cert that it should be getting from the server. Having removed that odd char I came across this error. that said the "bulk edit option" should take newline to mean "ok new header". Turns out that space after token was actually a newline char (odd that postman didn't trim that as it's never valid to have newline in all the headers i've come across so far (is this ever valid?).
#Postman app for chrome how to#
Straight up weird, no idea how to solve that. So I took a look in my certs list under settings and found this. I opened up the postman dev tools and console to see if I could figure out more about what was going on.įirst up I get this error in the console. Ok did some digging (after yet another postman reinstall.
0 kommentar(er)
