In my experience of using the traffic inspection tool fiddler: for https sites you have to have it add its own self signed cert to be able to see traffic.
Firefox, out of the box, detects it immediately and warns you of a security issue, not letting you do anything.
Chrome, and chromium based browsers,
don’t even notice it and happily let you do what needs to be done.
I’ve had the experience of a few sites not working recently in Firefox, one of them explicitly stated an ad server was blocked because of xss settings and refused to load. Chrome didn’t care.
Because Firefox has better XSS detection than Chrome and will block adware sites from injecting tracking that Chrome completely allows.
is this true?
In my experience of using the traffic inspection tool fiddler: for https sites you have to have it add its own self signed cert to be able to see traffic.
Firefox, out of the box, detects it immediately and warns you of a security issue, not letting you do anything.
Chrome, and chromium based browsers,
don’t even notice it and happily let you do what needs to be done.
I’ve had the experience of a few sites not working recently in Firefox, one of them explicitly stated an ad server was blocked because of xss settings and refused to load. Chrome didn’t care.