[GH-ISSUE #210] Support Wildcard for SSL Proxying domains #207

Open
opened 2026-03-03 19:16:12 +03:00 by kerem · 3 comments
Owner

Originally created by @NghiaTranUIT on GitHub (Jul 8, 2019).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/210

Originally assigned to: @NghiaTranUIT on GitHub.

🐶 Brief

Some users request that it would be great if they are able to add

  • api*.domain.com for api1.domain.com or api2.domain.com
    • => for all out going requests
  • ..

👑 Criteria

  • Able to match SSL Domains with wildcard * or /
  • Add basic instruction in HTTPS Response List windows
Originally created by @NghiaTranUIT on GitHub (Jul 8, 2019). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/210 Originally assigned to: @NghiaTranUIT on GitHub. ## 🐶 Brief Some users request that it would be great if they are able to add - `api*.domain.com` for api1.domain.com or api2.domain.com - * => for all out going requests - .. ## 👑 Criteria - [x] Able to match SSL Domains with wildcard * or / - [x] Add basic instruction in HTTPS Response List windows
Author
Owner

@NghiaTranUIT commented on GitHub (Jul 14, 2019):

We've supported TreeView (#208), so all flows, which match the node will be appended. It's slightly fulfill this feature.

For instance, if we pin api.producthunt.com/v1: "api.producthunt.com/v1/login", "api.producthunt.com/v1/posts", ... will be added.

It means I will push this feature later, since there are few essential features on the road map.

<!-- gh-comment-id:511170917 --> @NghiaTranUIT commented on GitHub (Jul 14, 2019): We've supported TreeView (#208), so all flows, which match the node will be appended. It's slightly fulfill this feature. For instance, if we pin `api.producthunt.com/v1`: "api.producthunt.com/v1/login", "api.producthunt.com/v1/posts", ... will be added. It means I will push this feature later, since there are few essential features on the road map.
Author
Owner

@shirshak55 commented on GitHub (Jan 29, 2020):

@NghiaTranUIT any status on this. It would be useful if we can just enable ssl for all domains. around 90% of all stuff uses https and even for api servers i mostly find irritating to enable it always and list has been growing too much.

In charles I used to do *.* so it would always decode ssl request i would like to see same for proxyman. Thanks.

<!-- gh-comment-id:579729620 --> @shirshak55 commented on GitHub (Jan 29, 2020): @NghiaTranUIT any status on this. It would be useful if we can just enable ssl for all domains. around 90% of all stuff uses https and even for api servers i mostly find irritating to enable it always and list has been growing too much. In charles I used to do `*.*` so it would always decode ssl request i would like to see same for proxyman. Thanks.
Author
Owner

@NghiaTranUIT commented on GitHub (Dec 8, 2020):

This request is supported in the 2.14.0 build (https://github.com/ProxymanApp/Proxyman/releases/tag/2.14.0).

Document at https://docs.proxyman.io/basic-features/ssl-proxying

<!-- gh-comment-id:740353386 --> @NghiaTranUIT commented on GitHub (Dec 8, 2020): This request is supported in the 2.14.0 build (https://github.com/ProxymanApp/Proxyman/releases/tag/2.14.0). Document at https://docs.proxyman.io/basic-features/ssl-proxying
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Proxyman#207
No description provided.