[GH-ISSUE #328] Execution request when using breakpoint always injects "?" to query param #324

Closed
opened 2026-03-03 19:17:28 +03:00 by kerem · 5 comments
Owner

Originally created by @leapful on GitHub (Nov 16, 2019).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/328

Originally assigned to: @NghiaTranUIT on GitHub.

Proxyman version? (Ex. Proxyman 1.4.3)

Proxyman 1.9.2

macOS Version? (Ex. mac 10.14)

macOS 10.16

Steps to reproduce

  1. Open Proxyman then open https://www.google.com/ in Chrome.
  2. Set breakpoint rule for https://www.google.com/ in Proxyman.
  3. Refresh https://www.google.com in Chrome.
  4. Breakpoint window in Proxyman will be prompted, then click execute to send request.
  5. The response url from google.com is now https://www.google.com/?

Expected behavior

Execution request from breakpoint should not inject any unexpected query param and response url for the steps to reproduce should be https://www.google.com/ .

This issue affects use case when testing caching for a website when server-side handling is using URL to get cache which should be, for example: "https://google.com" but now is "https://google.com/?" and causes cache not found.

Screenshots (optional)

Originally created by @leapful on GitHub (Nov 16, 2019). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/328 Originally assigned to: @NghiaTranUIT on GitHub. ### Proxyman version? (Ex. Proxyman 1.4.3) Proxyman 1.9.2 ### macOS Version? (Ex. mac 10.14) macOS 10.16 ### Steps to reproduce 1. Open Proxyman then open https://www.google.com/ in Chrome. 2. Set breakpoint rule for https://www.google.com/ in Proxyman. 3. Refresh https://www.google.com in Chrome. 4. Breakpoint window in Proxyman will be prompted, then click execute to send request. 5. The response url from google.com is now https://www.google.com/? ### Expected behavior Execution request from breakpoint should not inject any unexpected query param and response url for the steps to reproduce should be https://www.google.com/ . This issue affects use case when testing caching for a website when server-side handling is using URL to get cache which should be, for example: "https://google.com" but now is "https://google.com/?" and causes cache not found. ### Screenshots (optional)
kerem 2026-03-03 19:17:28 +03:00
Author
Owner

@NghiaTranUIT commented on GitHub (Nov 16, 2019):

Hey, thank for raising these issues. I'm able to reproduce it and it definitely affects the caching mechanism.

I will investigate and send you a hotfix build soon 👍

<!-- gh-comment-id:554646106 --> @NghiaTranUIT commented on GitHub (Nov 16, 2019): Hey, thank for raising these issues. I'm able to reproduce it and it definitely affects the caching mechanism. I will investigate and send you a hotfix build soon 👍
Author
Owner

@NghiaTranUIT commented on GitHub (Nov 16, 2019):

Hey @leapful, here is the Fix: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_1.9.2_Invalid_char_breakpoint.dmg

Please let me know if it works and I will release in the next build 👍

<!-- gh-comment-id:554652727 --> @NghiaTranUIT commented on GitHub (Nov 16, 2019): Hey @leapful, here is the Fix: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_1.9.2_Invalid_char_breakpoint.dmg Please let me know if it works and I will release in the next build 👍
Author
Owner

@leapful commented on GitHub (Nov 17, 2019):

@NghiaTranUIT Thanks for your fix. I'm able to finish my test scenario on caching.

<!-- gh-comment-id:554729851 --> @leapful commented on GitHub (Nov 17, 2019): @NghiaTranUIT Thanks for your fix. I'm able to finish my test scenario on caching.
Author
Owner

@NghiaTranUIT commented on GitHub (Nov 17, 2019):

Glad to hear that @leapful 👍

<!-- gh-comment-id:554735388 --> @NghiaTranUIT commented on GitHub (Nov 17, 2019): Glad to hear that @leapful 👍
Author
Owner

@NghiaTranUIT commented on GitHub (Nov 19, 2019):

@leapful This bug is fixed in the latest release Proxyman 1.9.3. Thank you so much 👍

<!-- gh-comment-id:555575600 --> @NghiaTranUIT commented on GitHub (Nov 19, 2019): @leapful This bug is fixed in the latest release [Proxyman 1.9.3](https://github.com/ProxymanApp/Proxyman/releases/tag/1.9.3). Thank you so much 👍
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#324
No description provided.