ProxymanApp / ProxymanApp/Proxyman
Wildcard domains not capturing as expected.
Open
@NghiaTranUIT is already working on this.
Since Feb 20, 2021.
✅ Done
bug
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Proxyman version? (Ex. Proxyman 1.4.3)
Proxyman Version 2.18.0 (21800)
macOS Version? (Ex. mac 10.14)
macOS 11.2.1 (20D74)
Steps to reproduce
- Add
cloudfunctions.netWildcard to SSL Proxy List - you will see thatcloudfunctions.net*gets added.... - Add
cloudfunctions.netWildcard to Allow White List, make sureInclude all Subpaths of this urlis checked. - Curl the following and notice Proxyman does not capture the result.:
curl "https://us-central1-test.cloudfunctions.net/sendLogTest"
- Remove the
cloudfunctions.net*Wildcard entry from SSL Proxy List and add*.cloudfunctions.net*. - Modify the
cloudfunctions.netWildcard entry from Allow List to be*.cloudfunctions.net*. - Perform step 3 again and notice the request is now captured.
Expected behavior
Proxyman should capture the request when entering SSL Proxy List and Allow List Wildcard domain to be cloudfunctions.net result without having to add *.cloudfunction.net* as a Wildcard which will work. Entering that is pretty much entering a Regex, the user expects that cloudfunction.net for both SSL Proxy List and Allow white list should capture this scenario.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.