ProxymanApp / ProxymanApp/Proxyman
Why `Map Remote` can't work with `Scripting` enabled?
Open
Nobody has claimed this yet.
bug
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Description
I have some URLs map remote enabled, for example, map remote https://host/path/* to http://192.168.1.1:8080/path/* , and it works fine.
But the map remote rule can't work when I add the script to URLs */path/*.
Steps to Reproduce
- Add map remote rule: https://host/path/* to http://192.168.1.1:8080/path/*
- Test the map remote rule, it works.
- Add Scripting rule: */path/* and add some string to the response body.
- Test map remote rule in step 1. It can't work.
Current Behavior
Map Remote can't work with Scripting enabled
Expected Behavior
Map Remote and Scripting both work fine.
Environment
- App version: Proxyman 4.9.0
- macOS version: macOS Ventura 13.4.1 (22F82) Apple M1
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.
Research direction
Start by reproducing the Map Remote and Scripting rule sequence from the issue on Proxyman 4.9.0 with macOS Ventura 13.4.1. Compare behavior with each rule enabled separately and together; done means both rules successfully apply to the same matching URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- devtools, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100