1907543 - [Rollout] Several “httpsfirst” schemeless metrics are not triggered in Private Browsing Mode

Status: RESOLVED DUPLICATE of bug 1891185

(Core :: DOM: Security, defect)

Description

[Carmen Fat [:cfat] - Ecosystem QA]

[Affected versions]:

• Firefox Release 125.0.3 (Build #20240425211020)
• Firefox Release 126.0 (Build #20240509170740)
• Firefox Release 127.0.2 (Build #20240624183754)
• Firefox Release 128.0 (Build #20240704121409)

[Affected Platforms]:

• Windows 10 x64
• macOS 14.4
• Ubuntu 22.04 x64

[Prerequisites]:

• Have the latest Firefox Release 128 installed.
• Have a browser profile enrolled in the HTTPS as default protocol rollout (https://experimenter.services.mozilla.com/nimbus/https-as-default-protocoll-in-address-bar/summary).

[Steps to reproduce]:

1. Open the browser from the prerequisites.
2. Open a Firefox Window that is in Private Mode (Ctrl+Shift+P).
3. Navigate to the insecure.httpsonly.polar.onl website.
4. Navigate to the timeout.httpsonly.polar.onl website.
5. Navigate to “about:glean” and add a tag name in the first field from About Testing.
6. Click the "Apply settings and submit ping" button.
7. Navigate to "https://debug-ping-preview.firebaseapp.com/pings/[YourTagName] to verify the metric ping.
8. Search for the following values:
   httpsfirst.downgraded_schemeless
   httpsfirst.downgrade_time_schemeless
   httpsfirst.downgraded_on_timer_schemeless

[Expected result]:

• The values are displayed in the metrics ping.

[Actual result]:

• The values are not displayed.

[Notes]:

• On versions 125.0 and 126.0 the "httpsfirst.upgraded_schemeless" metric is also missing, only the "httpsfirst.upgraded" version of the metric is displayed.

Comment 1

[Malte Jürgens [:maltejur]]

This is to be expected, as full HTTP-First is enabled in PBM. This means that instead of the httpsfirst.*_schemeless metrics being recorded, the same metrics will be recorded without the _schemeless suffix, even if the load is still coming from the address bar without a scheme. Can you confirm that you see the expected metrics without the schemeless suffix in the name?

Additionally, I think the differences with 125 and 126 are caused by the changes from Bug 1891185. But as I think we are in agreement with moving the rollout to 128 only due to Bug 1907553, I don't think this is going to be a problem.

Comment 2

[Frederik Braun [:freddy]]

We should just change the roll-out to target 128 as above.