Closed Bug 1596799 Opened 5 years ago Closed 5 years ago

Add a preference for socket peer port remapping

Categories

(Core :: Networking, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
mozilla74
Tracking Status
firefox74 --- fixed

People

(Reporter: mayhemer, Assigned: mayhemer)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

This is stage 1 for implementing bug 1523367 and for our current purposes probably quite sufficient for desktop and single-hosted test environments.

The idea is to have a pref like this:
network.socket.forcePort = "443,8443-8999=8081;80,808=8080"

All requests to default 443 and any port in range 8443 to 8999 will actually open to port 8081
All requests to default 80 and non-default 808 will go to port 8080.

When cross-used with network.dns.forceResolve we have a near-identical support for remapping as Chrome has, except that we can't map individual hosts, this pref applies to all but localhost and 127.0.0.1.

I'll leave bug 1523367 open for now if we need that.

Priority: -- → P2
Whiteboard: [necko-triaged]
Blocks: 1523367
Pushed by honzab.moz@firemni.cz: https://hg.mozilla.org/integration/autoland/rev/84f69fc66690 Have a preference to force remote TCP/UDP port remapping for easier local network testing, r=dragana
Pushed by honzab.moz@firemni.cz: https://hg.mozilla.org/integration/autoland/rev/eea4cd13b292 Have a preference to force remote TCP/UDP port remapping for easier local network testing, r=dragana
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: