Closed Bug 1906511 Opened 1 year ago Closed 1 year ago

Proxy configuration ignores exceptions

Categories

(Core :: Networking: Proxy, defect, P2)

defect

Tracking

()

RESOLVED DUPLICATE of bug 201685

People

(Reporter: ipv6only, Unassigned)

Details

(Whiteboard: [necko-triaged][necko-priority-next])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0

Steps to reproduce:

  1. I noticed that my ISP disabled IPv4 on my internet connection
  2. I configured Firefox to use a SOCKS proxy
  3. I also added an exception for the following IP ranges:
    ::/0, [::]/0

I apologize if this was reported before. I'm unable to search for existing bugs because this server is throwing server errors at me. Also the submit button on this form was disabled when I submitted this report. Had to reenable it using developer tools.

Firefox VErsion is 115.12.0esr (64-bit) from Debian

Actual results:

Firefox ignores the exception, no matter how the IP range is formatted.

When I try to make a connection via IPv6 (in this case, to an IPv6-only site), a TCP6 connection appears in netstat; However, this connection seems to lack a connection to a local process (huh?); EVen as root, I cannot see a PID. This connection remains in TIME_WAIT status indefinitely while Firefox takes the Proxy.

tcp6 0 0 (redacted):35854 (redacted):443 TIME_WAIT -

Expected results:

Proxy exceptions should be honored as configured.

The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Networking
Product: Firefox → Core
Version: other → unspecified
Severity: -- → S3
Component: Networking → Networking: Proxy
Priority: -- → P2
Whiteboard: [necko-triaged][necko-priority-next]

Might be duplicate of Bug 201685?

@manuel: THanks, I was unable to research existing bugs because bugzilla was throwing server errors at me which are now gone.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Duplicate of bug: 201685
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.