Closed Bug 1750655 Opened 3 years ago Closed 3 years ago

'Add Security Exception' dialog omits port number when trying to add CalDAV network calendar from server running on port 5006

Categories

(Thunderbird :: Security, defect)

defect

Tracking

(thunderbird_esr91+ fixed, thunderbird97 wontfix)

RESOLVED FIXED
98 Branch
Tracking Status
thunderbird_esr91 + fixed
thunderbird97 --- wontfix

People

(Reporter: Johannes.mozdev, Assigned: mkmelin)

References

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:95.0) Gecko/20100101 Firefox/95.0

Steps to reproduce:

I'm using Thunderbird 78.14.0 on Ubuntu 20.04.3 LTS and want to add a CalDAV network calendar in a fresh profile.
The URL looks like this: https://server:5006/Tausch/Kalender/Kalender
The server is a Synology DSM (6.2.4-25556 Update 2) and it's using a self-signed certificate.

Actual results:

I get the 'Add Security Exception' dialog, but the Location omits the port number 5006, it just have: server
So when clicking 'Confirm Security Exception', the port number 443 is added to server.
Therefore there is no connection possible and the dialog pop ups again.

Expected results:

The 'Add Security Exception' dialog should not omit the port number.

78 is end of life since quite some time. Please upgrade.

Assignee: nobody → mkmelin+mozilla
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → 98 Branch

I tested the daily build and can confirm that it works now as expected!
Thanks a lot!

Flags: needinfo?(Johannes.mozdev)

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/64575e67552c
when adding security exceptions, both hostname and port should be included when non-standard. r=darktrojan

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED

Comment on attachment 9259506 [details]
Bug 1750655 - when adding security exceptions, both hostname and port should be included when non-standard. r=darktrojan

[Approval Request Comment]
Regression caused by (bug #): unclear if it is a regression. maybe from cert override re-work
User impact if declined: can't add cert exception, and confusing experience if try to do so
Testing completed (on c-c, etc.): beta
Risk to taking this patch (and alternatives if risky): low risk

Attachment #9259506 - Flags: approval-comm-esr91?

Comment on attachment 9259506 [details]
Bug 1750655 - when adding security exceptions, both hostname and port should be included when non-standard. r=darktrojan

[Triage Comment]
Approved for esr91

Attachment #9259506 - Flags: approval-comm-esr91? → approval-comm-esr91+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: