Closed
Bug 1859576
Opened 1 year ago
Closed 1 year ago
When upgrading schemeless URLs from the address bar, Firefox does not log to the web developer tools
Categories
(Core :: DOM: Security, defect, P3)
Core
DOM: Security
Tracking
()
VERIFIED
FIXED
121 Branch
Tracking | Status | |
---|---|---|
firefox121 | --- | verified |
People
(Reporter: freddy, Assigned: maltejur)
References
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
STR:
- Enable
dom.security.https_first_schemeless
- Open the developer tools console
- Go to a website without a scheme (eg., example.com)
Expected behavior:
- We log that we upgraded a URL without a scheme to HTTPS
Actual behavior:
- We do not log.
- What I found is that the log message was sent to the global Browser Console and not to the right tab. It seems that the log call in https://searchfox.org/mozilla-central/source/dom/security/nsHTTPSOnlyUtils.cpp#443 is not targeting the right window.
Reporter | ||
Updated•1 year ago
|
Severity: -- → S3
Priority: -- → P3
Assignee | ||
Updated•1 year ago
|
Assignee: nobody → mjurgens
Status: NEW → ASSIGNED
Flags: needinfo?(mjurgens)
Assignee | ||
Comment 2•1 year ago
|
||
Updated•1 year ago
|
Whiteboard: [domsecurity-active]
Pushed by fbraun@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/92e66519460e
Try to log HTTPS-Only/First messages to triggering window of loadinfo if inner window does not exist yet r=freddyb
Comment 4•1 year ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox121:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
Updated•1 year ago
|
QA Whiteboard: [qa-121b-p2]
Comment 5•11 months ago
|
||
Reproduced the issue with 120.0a1 (2023-10-17) on Windows 10x64. After following STR from comment 0 no log message is displayed in the web console.
The issue is verified fixed with Firefox 121.0 on Windows 10x64, macOS 12 and Ubuntu 22. The HTTPS-First Mode: Upgrading URL loaded in the address bar without explicit protocol scheme to use HTTPS.
log message is displayed in the web console after following steps from comment 0.
Status: RESOLVED → VERIFIED
Has STR: --- → yes
QA Whiteboard: [qa-121b-p2]
You need to log in
before you can comment on or make changes to this bug.
Description
•