HttpBaseChannel::GetRemoteAddress fails when the channel is intercepted by a ServiceWorker

RESOLVED INVALID

Status

()

Core
Networking: HTTP
RESOLVED INVALID
3 years ago
3 years ago

People

(Reporter: baku, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox40 affected)

Details

(Reporter)

Description

3 years ago
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.
(Reporter)

Updated

3 years ago
Flags: needinfo?(josh)
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
Flags: needinfo?(josh)
(Reporter)

Updated

3 years ago
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.