Open Bug 1528449 Opened 5 years ago Updated 2 years ago

Can we still have non-HTTP channels with securityInfo?

Categories

(Core :: Networking, enhancement, P3)

enhancement

Tracking

()

Tracking Status
firefox67 --- affected

People

(Reporter: bzbarsky, Unassigned)

References

Details

(Whiteboard: [necko-triaged])

Once bug 1489308 is fixed and wyciwyg is gone, will the documentation for nsIChannel.securityInfo still be correct?

Honza, do you know the answer?

Flags: needinfo?(honzab.moz)
Priority: -- → P3
Whiteboard: [necko-triaged]

Found:

  1. https://searchfox.org/mozilla-central/source/modules/libjar/nsJARChannel.cpp#698
    which is unused: https://searchfox.org/mozilla-central/search?q=symbol:F_%3CT_nsJARChannel%3E_mSecurityInfo&redirect=false

  2. https://searchfox.org/mozilla-central/rev/b10ae6b7a50d176a813900cbe9dc18c85acd604b/netwerk/base/nsBaseChannel.cpp#482
    which is unused: https://searchfox.org/mozilla-central/search?q=symbol:F_%3CT_nsBaseChannel%3E_mSecurityInfo&redirect=false, https://searchfox.org/mozilla-central/search?q=symbol:_ZN13nsBaseChannel15SetSecurityInfoEP11nsISupports&redirect=false

Notes:

  • InterceptedHttpChannel derives from HttpBaseChannel and doesn't manipulate sec info

So, we can file a bugs to remove mSecurityInfo from nsJARChannel and nsBaseChannel.

And to answer: no, the documentation is outdated. We could even try to move the secinfo property away and let it live only on nsIHttpChannel. More correctly, have a new interface nsISecuredTransportChannel and expose it there, but that is likely an overkill these days ;)

Flags: needinfo?(honzab.moz)

(In reply to Dragana Damjanovic [:dragana] from comment #3)

There is nsBaseChannel

https://searchfox.org/mozilla-central/source/netwerk/base/nsBaseChannel.h#263

The member is never set a value.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.