[GH-ISSUE #1036] Copying request header raw data does not work properly. #1033

New issue

Open

opened 2026-03-03 19:23:58 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 19:23:58 +03:00

Owner

Originally created by @coolow on GitHub (Oct 17, 2021).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1036

Originally assigned to: @NghiaTranUIT on GitHub.

Proxyman version? (Ex. Proxyman 1.4.3)

Proxyman 1.5.0

macOS Version? (Ex. mac 10.14)

iOS 15.0.2

Steps to reproduce

Open a request A.
Click the View Raw button next to Header under the Request tab.
Click the Copy All menu item in the gear icon.
At this time, the header data of request A can be copied normally. Continue operations:
Open another request B.
Refer to the previous operations and use the Copy All function in request B.
At this time, the exception occurred, and the header data of request A was copied instead of the request B.

p.s. 1: If you continue to open other requests and use this copy function, the header data of request A is copied every time.
p.s. 2: After forcibly exiting the App, use this copy function again, except that the header data of the first request can be copied normally, and the header data of other requests can not be copied again. The situation is the same as previously described.
p.s. 3: In fact, the 4 functions Copy All, Copy Body Only, Share All, and Share the Body in the gear icon in step 3 all have this problem.

Expected behavior

Copying and sharing request header data works correctly.

Screenshots (optional)

Originally created by @coolow on GitHub (Oct 17, 2021). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1036 Originally assigned to: @NghiaTranUIT on GitHub. ### Proxyman version? (Ex. Proxyman 1.4.3) Proxyman 1.5.0 ### macOS Version? (Ex. mac 10.14) iOS 15.0.2 ### Steps to reproduce 1. Open a request A. 2. Click the **View Raw** button next to **Header** under the **Request** tab. 3. Click the **Copy All** menu item in the gear icon. At this time, the header data of request A can be copied normally. Continue operations: 4. Open another request B. 5. Refer to the previous operations and use the **Copy All** function in request B. At this time, the exception occurred, and the header data of request A was copied instead of the request B. p.s. 1: If you continue to open other requests and use this copy function, the header data of request A is copied every time. p.s. 2: After forcibly exiting the App, use this copy function again, except that the header data of the first request can be copied normally, and the header data of other requests can not be copied again. The situation is the same as previously described. p.s. 3: In fact, the 4 functions **Copy All**, **Copy Body Only**, **Share All**, and **Share the Body** in the gear icon in step 3 all have this problem. ### Expected behavior Copying and sharing request header data works correctly. ### Screenshots (optional)

kerem added the

bug

✅ Done

iOS

labels

2026-03-03 19:23:58 +03:00

kerem commented

2026-03-03 19:23:59 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Oct 18, 2021):

Thanks for the report @coolow 👍 It's a bug and we're going to fix it 🙌

@NghiaTranUIT commented on GitHub (Oct 18, 2021): Thanks for the report @coolow 👍 It's a bug and we're going to fix it 🙌

kerem commented

2026-03-03 19:23:59 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Oct 20, 2021):

@coolow Just a friendly reminder that your bug is fixed in build 1.5.2. It's in the review process and should go live soon 🙌

@NghiaTranUIT commented on GitHub (Oct 20, 2021): @coolow Just a friendly reminder that your bug is fixed in build 1.5.2. It's in the review process and should go live soon 🙌

kerem commented

2026-03-03 19:23:59 +03:00

Author

Owner

@coolow commented on GitHub (Oct 20, 2021):

@coolow Just a friendly reminder that your bug is fixed in build 1.5.2. It's in the review process and should go live soon 🙌

Glad to hear that. Thank you!

@coolow commented on GitHub (Oct 20, 2021): > @coolow Just a friendly reminder that your bug is fixed in build 1.5.2. It's in the review process and should go live soon 🙌 Glad to hear that. Thank you!