mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-25 16:15:55 +03:00
[GH-ISSUE #219] Do proxyman have transform response feature? #215
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#215
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 @thepinyo on GitHub (Jul 15, 2019).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/219
Originally assigned to: @NghiaTranUIT on GitHub.
@NghiaTranUIT commented on GitHub (Jul 15, 2019):
Yes, it's https://github.com/ProxymanApp/Proxyman/issues/118, which is our road map. It will release on Proxyman 1.4.6. Stay tuned 🎉
@thepinyo commented on GitHub (Jul 17, 2019):
@NghiaTranUIT good, i will await you.
@NghiaTranUIT commented on GitHub (Jul 19, 2019):
@thepinyo Just friendly reminder that simple version of Remap is "Remap response from file" #224 will be implemented in next version Proxyman 1.4.6 👍
@NghiaTranUIT commented on GitHub (Aug 1, 2019):
Hey @thepinyo,
It just post the BETA of this feature here https://github.com/ProxymanApp/Proxyman/issues/224#issuecomment-517331332. Let try it and let me know if you have any issues 🌮
@thepinyo commented on GitHub (Aug 1, 2019):
@NghiaTranUIT oh thank i'll try.
@NghiaTranUIT commented on GitHub (Aug 3, 2019):
@thepinyo the Proxyman 1.4.7 has officially been released now. Let check it out 👍
@thepinyo commented on GitHub (Aug 8, 2019):
how to change http status code of response.
@NghiaTranUIT commented on GitHub (Aug 8, 2019):
Hey @thepinyo
Currently, the Local map is not capable of manipulating the Status code of response. It's must be a ReWrite feature.
We're working the Breakpoint (able to change the Request data), then moving on to the ReWrite in next versions.
@thepinyo commented on GitHub (Aug 8, 2019):
good job bro, fighting 😉
@NghiaTranUIT commented on GitHub (Aug 25, 2019):
Hey @thepinyo, let check out Breakpoint on Proxyman 1.5.0 https://github.com/ProxymanApp/Proxyman/releases/tag/1.5.0
Get ready for the Breakpoint 😍
@robertoseidenberg commented on GitHub (May 6, 2020):
Is it possible that this feature is now broken? 🤔
Im using Proxyman 1.23.0 (12300) and I have not been able to get a breakpoint to fire on the response. If I put a breakpoint on an url for "request" and "response" Proxyman breaks two times but the UI always only shows the "request" data. Hence no way to edit the response.
@NghiaTranUIT commented on GitHub (May 6, 2020):
Hey @robertoseidenberg , can you share your screenshot when the Response panel doesn't appear on Breakpoint?
Here is how I set a breakpoint on a Response
@robertoseidenberg commented on GitHub (May 6, 2020):
Made you a .gif. I do remember having seen this on my computer as well but now it does not show up any more. Can not really say when it changed though. I'm sorry.
@NghiaTranUIT commented on GitHub (May 6, 2020):
Look like it’s a UI bug. Pls help me to reset the app from Help menu > Advanced > Reset
Then open on the big window size
@NghiaTranUIT commented on GitHub (May 6, 2020):
I will investigate tomorrow 👍
@NghiaTranUIT commented on GitHub (May 7, 2020):
Confirmed that it's a UI glitch if the size of Breakpoint windows is small. You can fix it by opening a big size and reset the app (Help -> Advanced -> Reset) @robertoseidenberg
@robertoseidenberg commented on GitHub (May 7, 2020):
Hey @NghiaTranUIT, sorry for the delay. I can confirm it's an UI bug. I did reset the app and fullsized the window and that helped. Thanks a lot for you fast response! App is awesome by the way. 😏
@NghiaTranUIT commented on GitHub (May 7, 2020):
Glad to hear that. I will fix it soon 👍
@robertoseidenberg commented on GitHub (May 7, 2020):
Thanks! The workaround works well enough for me meanwhile. I'm just super happy the feature is back. 😄