[GH-ISSUE #1929] Proxyman truncates URLs that contain a # symbol #1919

Open
opened 2026-03-03 19:55:27 +03:00 by kerem · 3 comments
Owner

Originally created by @adamprice on GitHub (Feb 7, 2024).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1929

Originally assigned to: @NghiaTranUIT on GitHub.

Description

Proxyman truncates URLs that contain a # symbol in the path when displaying them in the UI

Steps to Reproduce

  1. Navigate to any URL that contains a # symbol in the path

Current Behavior

Any part of the URL after the # symbol doesn't display in the Proxyman UI

Expected Behavior

The full URL should be displayed in the UI

Environment

  • App version: Proxyman 4.16.0
  • macOS version: macOS Ventura 13.6.1
Originally created by @adamprice on GitHub (Feb 7, 2024). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1929 Originally assigned to: @NghiaTranUIT on GitHub. ## Description Proxyman truncates URLs that contain a # symbol in the path when displaying them in the UI ## Steps to Reproduce 1. Navigate to any URL that contains a # symbol in the path ## Current Behavior Any part of the URL after the # symbol doesn't display in the Proxyman UI ## Expected Behavior The full URL should be displayed in the UI ## Environment - App version: Proxyman 4.16.0 - macOS version: macOS Ventura 13.6.1
Author
Owner

@NghiaTranUIT commented on GitHub (Feb 9, 2024):

Thanks, it's a critical bug, I'm not sure why the fragment of the URL is ignored. Gonna fix it now and send you a Beta build 👍

<!-- gh-comment-id:1935252237 --> @NghiaTranUIT commented on GitHub (Feb 9, 2024): Thanks, it's a critical bug, I'm not sure why the fragment of the URL is ignored. Gonna fix it now and send you a Beta build 👍
Author
Owner

@NghiaTranUIT commented on GitHub (Feb 9, 2024):

@adamprice turns out the fragment from the URL is never sent in the HTTP Request Message. Thus, Proxyman can't capture it.

You can verify it by Google Chrome Dev Tool.

CleanShot 2024-02-09 at 12 00 51@2x

This blog also confirmed this behavior: https://blog.httpwatch.com/2011/03/01/6-things-you-should-know-about-fragment-urls/

<!-- gh-comment-id:1935337193 --> @NghiaTranUIT commented on GitHub (Feb 9, 2024): @adamprice turns out the fragment from the URL is never sent in the HTTP Request Message. Thus, Proxyman can't capture it. You can verify it by Google Chrome Dev Tool. ![CleanShot 2024-02-09 at 12 00 51@2x](https://github.com/ProxymanApp/Proxyman/assets/5878421/ab1b8ff8-9ec7-4ba2-8999-0bc2f8318fe8) This blog also confirmed this behavior: https://blog.httpwatch.com/2011/03/01/6-things-you-should-know-about-fragment-urls/
Author
Owner

@adamprice commented on GitHub (Feb 9, 2024):

TIL!

Thanks for looking into it so quickly 👍🏻

<!-- gh-comment-id:1936216280 --> @adamprice commented on GitHub (Feb 9, 2024): TIL! Thanks for looking into it so quickly 👍🏻
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#1919
No description provided.