starred/Proxyman

Fork 0

mirror of https://github.com/ProxymanApp/Proxyman.git synced 2026-04-25 16:15:55 +03:00

[GH-ISSUE #1578] Ability to rewrite display values in request/response panels #1571

New issue

Open

opened 2026-03-03 19:52:33 +03:00 by kerem · 9 comments

kerem commented

2026-03-03 19:52:33 +03:00

Owner

Originally created by @jacobbednarz on GitHub (Mar 16, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1578

Originally assigned to: @NghiaTranUIT on GitHub.

Description

A part of my day to day is either showing people how to debug network issues or putting together videos for how to debug some of these issues. While every effort is made to redact sensitive information from being shown in the request and response panels, sometimes, it will be shown.

Unsure of the specific implementation but similar to scripting it would be cool if I could write functionality to only change the rendered values not the actual values (which is why I can't use scripting as is). For example, if there is a HTTP authorization header in the request, rewrite the panel output to be Authorization: [redacted] unless I somehow toggle it off. The actual authorization value would still be sent correctly though.

Why this feature/change is important?

This would allow Proxyman to be redact any potentially sensitive information in display panels instead of allowing them to be presented or redacted after the fact.

Originally created by @jacobbednarz on GitHub (Mar 16, 2023). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1578 Originally assigned to: @NghiaTranUIT on GitHub. ## Description A part of my day to day is either showing people how to debug network issues or putting together videos for how to debug some of these issues. While every effort is made to redact sensitive information from being shown in the request and response panels, sometimes, it will be shown. Unsure of the specific implementation but similar to [scripting](https://docs.proxyman.io/scripting/script) it would be cool if I could write functionality to **only change the rendered values** not the actual values (which is why I can't use scripting as is). For example, if there is a HTTP authorization header in the request, rewrite the panel output to be `Authorization: [redacted]` unless I somehow toggle it off. The actual authorization value would still be sent correctly though. ## Why this feature/change is important? This would allow Proxyman to be redact any potentially sensitive information in display panels instead of allowing them to be presented or redacted after the fact.

kerem added the

enhancement

label

2026-03-03 19:52:33 +03:00

kerem commented

2026-03-03 19:52:34 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Mar 16, 2023):

Thanks for your suggestion 👍

Some users also request this feature. Basically, they would use Scripting to modify the Body for Previewer, but not actually change the real body. In some use cases, they would like to decrypt the body or parse the data to text-based.

I suggest:

async function onRequest(context, url, request) {

  // change the preview data
  request. preview.body = {
    "id": 123
  }
  request. preview.header = []
  return request;
}

@NghiaTranUIT commented on GitHub (Mar 16, 2023): Thanks for your suggestion 👍 Some users also request this feature. Basically, they would use Scripting to modify the Body for Previewer, but not actually change the real body. In some use cases, they would like to decrypt the body or parse the data to text-based. I suggest: ```javascript async function onRequest(context, url, request) { // change the preview data request. preview.body = { "id": 123 } request. preview.header = [] return request; } ```

kerem commented

2026-03-03 19:52:34 +03:00

Author

Owner

@jacobbednarz commented on GitHub (Mar 16, 2023):

to clarify, do you mean that this works today using the above snippet? or that is you aspirational API for it?

@jacobbednarz commented on GitHub (Mar 16, 2023): to clarify, do you mean that this works today using the above snippet? or that is you aspirational API for it?

kerem commented

2026-03-03 19:52:34 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Mar 17, 2023):

It hasn't been implemented yet, it's just my proposal 👍 Using Scripting rather than introducing a new GUI tool.

@NghiaTranUIT commented on GitHub (Mar 17, 2023): It hasn't been implemented yet, it's just my proposal 👍 Using Scripting rather than introducing a new GUI tool.

kerem commented

2026-03-03 19:52:34 +03:00

Author

Owner

@jacobbednarz commented on GitHub (Mar 17, 2023):

thanks for clarifying as i thought i had missed this and was eagerly digging through the tools 😄

@jacobbednarz commented on GitHub (Mar 17, 2023): thanks for clarifying as i thought i had missed this and was eagerly digging through the tools 😄

kerem commented

2026-03-03 19:52:34 +03:00

Author

Owner

@4332weizi commented on GitHub (Jun 28, 2023):

Hi, any update?

@4332weizi commented on GitHub (Jun 28, 2023): Hi, any update?

kerem commented

2026-03-03 19:52:34 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Jun 28, 2023):

I will put this feature to 4.9.0 👍

@NghiaTranUIT commented on GitHub (Jun 28, 2023): I will put this feature to 4.9.0 👍

kerem commented

2026-03-03 19:52:34 +03:00

Author

Owner

@dafong commented on GitHub (Jul 18, 2023):

does 4.9.0 contain this feature? I can't find the preview in

@dafong commented on GitHub (Jul 18, 2023): does 4.9.0 contain this feature? I can't find the preview in ![image](https://github.com/ProxymanApp/Proxyman/assets/1400296/6b2636cf-204d-48ad-bcab-ca7eee7542f4)

kerem commented

2026-03-03 19:52:34 +03:00

Author

Owner

@dafong commented on GitHub (Jul 31, 2023):

any update?

@dafong commented on GitHub (Jul 31, 2023): any update?

kerem commented

2026-03-03 19:52:34 +03:00

Author

Owner

@jacobbednarz commented on GitHub (Aug 1, 2023):

@dafong please don't keep pestering on a public issue for an update. if there was an update, it would have been provided here or in the release notes. all you're doing here is ping everyone else who is patiently subscribed to the issue.

@jacobbednarz commented on GitHub (Aug 1, 2023): @dafong please don't keep pestering on a public issue for an update. if there was an update, it would have been provided here or in the release notes. all you're doing here is ping everyone else who is patiently subscribed to the issue.