[GH-ISSUE #273] [Plugin] Base64 Decoder #271

Open
opened 2026-03-03 19:16:58 +03:00 by kerem · 7 comments
Owner

Originally created by @NghiaTranUIT on GitHub (Sep 6, 2019).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/273

Originally assigned to: @NghiaTranUIT on GitHub.

🐶 Brief

I would be great if we support plugin to enable decoding the Request/Response to desired format. It could be base64, thrift or protobuf, so we can quickly see the content.

👑 Criteria

  • Support plugin: Base64 Decoder
  • Able to decode the data in body, header, query or encoded-form in request or response.
Originally created by @NghiaTranUIT on GitHub (Sep 6, 2019). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/273 Originally assigned to: @NghiaTranUIT on GitHub. ## 🐶 Brief I would be great if we support plugin to enable decoding the Request/Response to desired format. It could be base64, thrift or protobuf, so we can quickly see the content. ## 👑 Criteria - [ ] Support plugin: Base64 Decoder - [x] Able to decode the data in body, header, query or encoded-form in request or response.
Author
Owner

@shirshak55 commented on GitHub (Sep 14, 2019):

yea you should give us ability to able to decode information. May be support so that we can make js or python or rust plugin so we can add many more decoding support?

<!-- gh-comment-id:531490858 --> @shirshak55 commented on GitHub (Sep 14, 2019): yea you should give us ability to able to decode information. May be support so that we can make js or python or rust plugin so we can add many more decoding support?
Author
Owner

@NghiaTranUIT commented on GitHub (Sep 15, 2019):

I'm thinking how to add this base64 decoded on right menu-context @shirshak55

Screen Shot 2019-09-15 at 20 38 23

However, the problem is that some response doesn't entirely encode in base64, it's just some values in JSON response. Or somecase, the base64-encoded string is in the query's URL

<!-- gh-comment-id:531566390 --> @NghiaTranUIT commented on GitHub (Sep 15, 2019): I'm thinking how to add this base64 decoded on right menu-context @shirshak55 <img width="538" alt="Screen Shot 2019-09-15 at 20 38 23" src="https://user-images.githubusercontent.com/5878421/64922394-fdb6fd00-d7f8-11e9-8270-f9a1502c0517.png"> However, the problem is that some response doesn't entirely encode in base64, it's just some values in JSON response. Or somecase, the base64-encoded string is in the query's URL
Author
Owner

@shirshak55 commented on GitHub (Sep 15, 2019):

it can be decided according to header right?

<!-- gh-comment-id:531570206 --> @shirshak55 commented on GitHub (Sep 15, 2019): it can be decided according to header right?
Author
Owner

@Robert-Saiter commented on GitHub (Nov 19, 2019):

Could you do this with a simple right click option? Highlight the text->Right Click->Decode Selected Text?

<!-- gh-comment-id:555565399 --> @Robert-Saiter commented on GitHub (Nov 19, 2019): Could you do this with a simple right click option? Highlight the text->Right Click->Decode Selected Text?
Author
Owner

@NghiaTranUIT commented on GitHub (Nov 19, 2019):

For now, we can base64 decode entire response body from https://github.com/ProxymanApp/Proxyman/issues/320

The ideal to put the Base64 decode and form in the Menu Context for the selected text is remarkable. I will definitely support it in the next release. Thank for bump it @S8ER01Z 👍

<!-- gh-comment-id:555569756 --> @NghiaTranUIT commented on GitHub (Nov 19, 2019): For now, we can base64 decode entire response body from https://github.com/ProxymanApp/Proxyman/issues/320 The ideal to put the Base64 decode and form in the Menu Context for the selected text is remarkable. I will definitely support it in the next release. Thank for bump it @S8ER01Z 👍
Author
Owner

@Robert-Saiter commented on GitHub (Dec 12, 2019):

I see this in 1.10.0 and wanted to ask about behavior. When I select / highlight a base64 encoded section of text I get an error <Invalid Base64 String> even though the portion of text highlighted will decode fine as base64 (Example: d3d3LmZhY2Vib29rLmNvbS8 ). The section highlighted is in the path string so I wasn't sure if it is using the selected text for decoding or trying to use the entire path. Can you comment?

Path - /broker?reason=&categoryid=8192&policyid=0&i2n=2706595643&url=d3d3LmZhY2Vib29rLmNvbS8=&ssl=true&pac=true&rand=162820312
Highlighted selection - d3d3LmZhY2Vib29rLmNvbS8

<!-- gh-comment-id:564837762 --> @Robert-Saiter commented on GitHub (Dec 12, 2019): I see this in 1.10.0 and wanted to ask about behavior. When I select / highlight a base64 encoded section of text I get an error `<Invalid Base64 String>` even though the portion of text highlighted will decode fine as base64 (Example: _**d3d3LmZhY2Vib29rLmNvbS8**_ ). The section highlighted is in the path string so I wasn't sure if it is using the selected text for decoding or trying to use the entire path. Can you comment? Path - **_/broker?reason=&categoryid=8192&policyid=0&i2n=2706595643&url=d3d3LmZhY2Vib29rLmNvbS8=&ssl=true&pac=true&rand=162820312_** Highlighted selection - _**d3d3LmZhY2Vib29rLmNvbS8**_
Author
Owner

@NghiaTranUIT commented on GitHub (Dec 12, 2019):

For now, it's impossible to know which portion of the selected text could be base64-decoded.

So, you have to select the base64 encoded string. Ex: d3d3LmZhY2Vib29rLmNvbS8

<!-- gh-comment-id:564844758 --> @NghiaTranUIT commented on GitHub (Dec 12, 2019): For now, it's impossible to know which portion of the selected text could be base64-decoded. So, you have to select the base64 encoded string. Ex: **d3d3LmZhY2Vib29rLmNvbS8**
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Proxyman#271
No description provided.