mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-27 00:55:57 +03:00
[GH-ISSUE #901] iOS simulator SSL handshake failure on some subdomains #896
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#896
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @EricMentele on GitHub (May 28, 2021).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/901
Originally assigned to: @NghiaTranUIT on GitHub.
Proxyman version? (Ex. Proxyman 1.4.3)
Version 2.26.0 (22600) free version
macOS Version? (Ex. mac 10.14)
Big Sur 11.4
Steps to reproduce
Install Mac OS Cert and cert on open simulators with reboot
Cert is trusted
Login to app
Error bad request in app.
Proxyman SSL handshake failure 999 on one subdomain.
Expected behavior
All calls succeed and show payloads in json format
Screenshots (optional)
@EricMentele commented on GitHub (May 28, 2021):
Happy to jump on a call with you if it will help.
@NghiaTranUIT commented on GitHub (May 28, 2021):
Hi, I'm not sure what caused the error on this particular domain 🤔
I tried to get this domain and it works on my end.
@EricMentele Can you help me to execute this command in your Terminal app? (Please make sure Proxyman app is opening), and see if you're able to see the HTTPS Response 👍
@EricMentele commented on GitHub (May 28, 2021):
@NghiaTranUIT commented on GitHub (May 28, 2021):
So it works from curl but doesn't work from your iOS Simulator.
From what I see in your first screenshot, you're able to see other HTTPS Requests from iOS Simulator, which means the certificate is installed and trusted properly.
Just wondering: Does this issue happen in your real iOS Device or it happens only with iOS Simulator?
@EricMentele commented on GitHub (May 28, 2021):
It doesn't work. That has an error. On the simulator two calls work and one gets an ssl handshake failure.
@EricMentele commented on GitHub (May 28, 2021):
It's strange because the MacOs proxy seems to work. Tested it on Google.com and also the two calls from the app from the simulator. Haven't tried it on device because I need it to work on the simulator.
@EricMentele commented on GitHub (May 28, 2021):
I have Charles Proxy and it can't even install certs on the simulator anymore.
@NghiaTranUIT commented on GitHub (May 28, 2021):
Thanks for getting back. You can fix the Charles Proxy by following this answer: https://stackoverflow.com/a/67297897/3127477
and try to use Charles Proxy to see if you're able to reproduce the bug 🤔
I'm not sure why only this domain doesn't work. If it's a bug from Proxyman, I suppose you couldn't see any Request from your iOS Simulator.
@EricMentele commented on GitHub (May 28, 2021):
I tried the manual root cert; however, my admin account gets rejected. It would be great to get Proxyman working because I like it more.
@EricMentele commented on GitHub (May 28, 2021):
Strange... now I don't see any traffic from the simulator.
@EricMentele commented on GitHub (May 28, 2021):
Saw this in the earlier terminal output: * ALPN, server did not agree to a protocol
@EricMentele commented on GitHub (May 28, 2021):
Very strange. I rebooted Proxyman and now it only shows firebase and doesn't seem to log any other traffic even though ssl is active for the app.
@EricMentele commented on GitHub (May 28, 2021):
The app calls are all succeeding without being recorded. Thank you for trying to help. I understand if this is too weird of an issue spend time on. Did not used to have it and think it may be related to an Xcode update.
@NghiaTranUIT commented on GitHub (May 28, 2021):
Sorry to hear that.
It's correct behavior because Proxyman doesn't support HTTP/2 yet, so ALPN would use HTTP/1.1 => cURL will print this warning.
Regarding the issue, I would like to suggest:
Meanwhile, I will investigate the bug
@EricMentele commented on GitHub (May 28, 2021):
I just tried Charles and it told me no devices are booted, when installing the cert... Used the command line version of the link you sent me. That is odd because I have a simulator open and running.
@EricMentele commented on GitHub (May 28, 2021):
I found the issue!
"Similar scenario with iOS14.
The SSL certificate is approved for a subdomain with a wild card (*.enabley.io). We noticed that when the prefix of the wildcard contains underscore (e.g. better_office.enabley.io), the certificate is not recognized. However when the prefix doesn't contain underscore (betteroffice.enabley.io), everything works perfectly.
Any clues?"
The failing domain on my simulator has an _
https://developer.apple.com/forums/thread/655074
@NghiaTranUIT commented on GitHub (May 28, 2021):
Thanks for the link @EricMentele 🌮
Look like it's the issue from the Networking library from Apple (URLSession), which automatically rejected the HTTPS
https://fhir-staging.medinformatix.cc, which doesn't match the certificate.Therefore, we could not do anything to fix it.
You should raise this issue to your team, and update the domain in order to make it work 🌮
@NghiaTranUIT commented on GitHub (May 28, 2021):
Hmm, sorry, look like the domain is already correct
https://fhir-staging.medinformatix.cc(no underscore)@EricMentele commented on GitHub (May 28, 2021):
The underscore is in the full path: getEncountersForPatientId URL https://fhir-staging.medinformatix.cc/v3/Encounter?patient=T500014&_include=*
@EricMentele commented on GitHub (May 28, 2021):
I reached out to my team and asked them if we can replace underscores. Thank you for your help!
@EricMentele commented on GitHub (May 28, 2021):
Problem solved. I had a space in a request header string... 🤦♂️ @NghiaTranUIT
@NghiaTranUIT commented on GitHub (May 29, 2021):
Glad to know you finally fix a bug 😄 🌮