mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-26 16:45:57 +03:00
[GH-ISSUE #1606] Aborting requests #1599
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#1599
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 @KirillKornev on GitHub (Apr 19, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1606
Originally assigned to: @NghiaTranUIT on GitHub.
Description
Hi! Could you help me?
In old versions I often used aborting requests in breakpoint screen.
It worked perfect, I got result on the screen(my device) immediately and device got an error. We used aborting for testing scenarios when user got en error from backend for current request.
After update to version 4.6.1 something changed and aborting request abort it, but my device just make new requests, time after time try to call new request. It now looks like you don't have an internet connection.
Is it possible to change some settings to abort requests like in old versions?
Thank you!
@KirillKornev commented on GitHub (Apr 19, 2023):
Just for clear understanding attached an screenshot.
I tap abort button, but my request call again and again.
In old version it was aborted and I got an error on device.
@NghiaTranUIT commented on GitHub (Apr 19, 2023):
Thanks. On the latest version, we change the behavior of aborting, instead of close the connection immediately, it returns 503 error.
I will revert it and add options to choose which behavior it should be.
@KirillKornev commented on GitHub (Apr 19, 2023):
Thank you!
I hope it will be fixed in the next versions.
@NghiaTranUIT commented on GitHub (Apr 19, 2023):
I will fix and send you a Beta build tomorrow 👍
@NghiaTranUIT commented on GitHub (Apr 19, 2023):
@KirillKornev let's use this beta build: https://download.proxyman.io/beta/Proxyman_4.6.1_Fix_breakpoint_abort.dmg
You can simply select the Abort behavior in the Abort submenu. You should select "Return 503 status code", which a previous logic.
@KirillKornev commented on GitHub (Apr 19, 2023):
Really fast answer. Thanks!