-
Notifications
You must be signed in to change notification settings - Fork 839
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explicit 443 is not the same as implicit 443 when using client certificates #4707
Comments
@abatishchev This is a verified bug. We are working on fixing this. |
++1 on this one. We are using this feature for Open Banking, in the financial sector, and this bug is really affecting the user experience for our all community: We decided to use postman as a way of documenting/exploring the Open Banking standard, we really like to see this issue fixed soon. |
+1 |
Any updates on the fix @numaanashraf? |
We've released a fix for this on our Canary ( @abatishchev @qcastel @benjefferies Please try it out in the Canary version and let us know if you continue to face the issue. |
This has been fixed in the latest Postman app. |
Describe the bug:
Port is treated literally when client certificate is chosen from settings
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If port 443 was specified in settings then it's treated the same way if it was omitted.
App information (please complete the following information):
The text was updated successfully, but these errors were encountered: