Closed Bug 1747673 Opened 4 years ago Closed 4 years ago

HTTPS First in PBM breaks http://docs.imsidesign.com/

Categories

(Core :: DOM: Security, defect, P2)

Firefox 95
defect

Tracking

()

RESOLVED FIXED
98 Branch
Tracking Status
firefox98 --- fixed

People

(Reporter: jscher2000, Assigned: t.yavor)

References

(Blocks 1 open bug)

Details

(Whiteboard: [domsecurity-active])

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:95.0) Gecko/20100101 Firefox/95.0

Steps to reproduce:

Navigate to http://docs.imsidesign.com/projects/TurboCAD-2021/turbocad-2021-user-guide-publication/Customized-Programming/Parametric-Part-Script-Editing/ in a regular window and a private window.

Actual results:

Regular window: page loaded fine.

Private window: HTTPS First redirected and server (Cloudflare) returned 521 error.

Expected results:

Since HTTPS First doesn't allow user exceptions, could it handle this kind of error as a potential connection issue?

More generally, HTTPS First is an underdocumented feature that is difficult to troubleshoot on SUMO. https://support.mozilla.org/questions/1362289

Component: General → DOM: Security

This seems closely related to bug 1729618, possibly a duplicate. See the issues reported there and the comments.

Assignee: nobody → lyavor
Status: UNCONFIRMED → NEW
Ever confirmed: true

I can reproduce the bug. It occurs since https-first (till now) only consider to downgrade requests with a response error status between 400 - 511 (https://searchfox.org/mozilla-central/source/dom/security/nsHTTPSOnlyUtils.cpp#474-475).
That should probably adjust to 400 - 525.

Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [domsecurity-active]

The severity field is not set for this bug.
:ckerschb, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(ckerschb)
Severity: -- → S3
Flags: needinfo?(ckerschb)
Pushed by mozilla@christophkerschbaumer.com: https://hg.mozilla.org/integration/autoland/rev/0d863192031a HTTPS First fallback to http for non-standard 5xx status code responses. r=ckerschb,kershaw
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 98 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: