The main reason is because we don't set the mPeerAddr and the mSelfAddr as we do for a 'normal' nsIHttpChannel: Usually we set these 2 addresses in mozilla::net::nsHttpChannel::OnTransportStatus(). I guess we should cache those 2 addresses or synthesize them as we do for the other network element of the nsIHttpChannel.
Does it actually make sense to synthesize a value for a peer address? We're not making a real connection anywhere.
Component: DOM → Networking: HTTP
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.