Propose documentation updated regarding Chrome settings when using proxyman.debug domain

[ramiroaraujo]

Description

Didn't know where to file this, it's not a bug, but it's a missing documentation info that was hard for me to figure out. When modifying /etc/hosts to resolve proxyman.debug to 127.0.0.1 as indicated here Proxyman can show traffic as expected but for example Chrome marks this site as "Not secure" in a different way that when using localhost, and it disallows you to grant permissions such as Location, Camera, Microphone and others. Same when using localhost.proxyman.io.

The solution for this, in cases where it might be needed, is to go to chrome://flags/, search for the setting #unsafely-treat-insecure-origin-as-secure, enable it, set the URL with domain and ports separated by commas such as http://proxyman.debug:3000,http://proxyman.debug:3001 and re-launch Chrome.

[NghiaTranUIT]

Chrome marks this site as "Not secure" in a different way that when using localhost

It's expected behavior because it's HTTP, not HTTPS http://proxyman.debug:3000.

it disallows you to grant permissions such as Location, Camera, Microphone and others.

Thanks for letting me know, I guess it's Chrome Security, which only enables it on HTTPS or Production Mode.

The solution for this, in cases where it might be needed, is to go to chrome://flags/, search for the setting #unsafely-treat-insecure-origin-as-secure, enable it, set the URL with domain and ports separated by commas such as http://proxyman.debug:3000,http://proxyman.debug:3001 and re-launch Chrome.

Thanks. I will add your update to the Docs 👍