mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-29 10:05:52 +03:00
[GH-ISSUE #1651] Uncontrolled automatic sending of requests #1643
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#1643
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 @907352qq on GitHub (May 23, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1651
Originally assigned to: @NghiaTranUIT on GitHub.
Description
I have found a problem, when I request a url that does not exist, the software will automatically send the request repeatedly, for example, if I request "http://127.0.0.1:9090" in my browser. I don't know if it's a problem with my operation or with the software, but I'd appreciate an answer!
@NghiaTranUIT commented on GitHub (May 24, 2023):
@907352qq Proxyman doesn't send the request repeatedly. If it's an invalid URL, it just sends back the response and stops the socket.
Do you have any screenshot to show that it's repeated?
@907352qq commented on GitHub (May 25, 2023):
And I only request for it once in my browser.
Requests are still coming in.
Proxyman Version:4.8.0
@907352qq commented on GitHub (May 25, 2023):
I also tried to restore the factory settings, no effect.
@NghiaTranUIT commented on GitHub (May 25, 2023):
I see: The problem is why do you have access to
http://127.0.0.1:9090🤔Port 9090 is listening by Proxyman, so if you directly access this port, Proxyman might cause an infinite loop bug. I'm going to fix it now.
If you'd like to capture
http://localhost:3000, for example, it should work and there is no loop bug.Follow this document to make sure Proxyman can capture
localhostrequest: https://docs.proxyman.io/troubleshooting/couldnt-see-any-request-from-localhost-server@NghiaTranUIT commented on GitHub (May 25, 2023):
@907352qq Fixed: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_4.8.0_Fix_infinite_loop.dmg
@907352qq commented on GitHub (May 25, 2023):
I used Charles before, this is how I intended to use it:

It would be great if this could be implemented so that I don't have to set up anything else.
I now use a reverse proxy to solve the problem as well.
Thanks.
@NghiaTranUIT commented on GitHub (May 26, 2023):
@907352qq you can check out the Reverse Proxy Tutorial: https://proxyman.io/posts/2023-03-22-How-to-use-Reverse-Proxy
Not sure what is the source of your Request? Is it from NodeJS Server, Python, or Ruby? If yes, instead of using the Reverse Proxy, which is complicated to setup, you can use the Automatic Setup: https://docs.proxyman.io/automatic-setup/automatic-setup
It helps you:
NodeJS: Axios, got, superagent, fetch, and node-fetch
Python: http, https, aiohttp, requests
Ruby: http, net/http, net/htps, faraday, and httparty, fastlane
ElectronJS
cURL