ProxymanApp / ProxymanApp/Proxyman
make all rule responses to have CORS headers built-in
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Description
we get multiple times CORS errors in the browsers for different JS or other files. I want to have inside the Rule setting, for a specific path, an option to add all CORS headers with the option to change it to the domain it arrived from (this is because of Apple devices that sometimes not like the "*" value).
Why this feature/change is important?
it save LOTS LOTS of time in just enable and disable it. we, as a team, spend lots of time on that and working with Proxyman Scripts without a real need. and then... we forget to close it and waisting time finding why the Proxyman is "not working" until find that Scripts is ON.
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
No source files or tests are named. Start by tracing how Rule settings apply response headers, then review the existing CORS and Proxyman Scripts behavior; done means a rule can enable the requested CORS headers and choose the requesting domain instead of "*".
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100