Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Custom protocol should not have "connection is not secure" dropdown #38

Closed
Gozala opened this issue Jul 23, 2018 · 1 comment
Closed

Custom protocol should not have "connection is not secure" dropdown #38

Gozala opened this issue Jul 23, 2018 · 1 comment
Labels
Protocol Protocol API related issues

Comments

@Gozala
Copy link
Contributor

Gozala commented Jul 23, 2018

This is followup from #2 where you can find all the details. Below quote is short summary:

Unfortunately I discovered yet another issue this time it's a clam that connection is not secure:

screen shot 2018-05-22 at 4 07 14 pm

And I have also verified it's not related to the isSecureContext as that even with system principal same error seems to appear. I am suspecting it's related to securityInfo field of nsIChannel.
@Gozala Gozala added the Protocol Protocol API related issues label Jul 23, 2018
@Gozala
Copy link
Contributor Author

Gozala commented Aug 7, 2019

Migrate to https://bugzilla.mozilla.org/show_bug.cgi?id=1572217

@Gozala Gozala closed this as completed Aug 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Protocol Protocol API related issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Gozala