1853574 - Firefox does not use the correct APN proxy port on mobile data

Status: RESOLVED DUPLICATE of bug 1858377

(Core :: Networking: HTTP, defect)

Description

[reconman]

Attachment: Network logs

Steps to reproduce:

1. Use a mobile provider where the APN proxy is not using port 80 (8001 in my case)
2. Turn off WiFi
3. Load any website

Actual results:

No websites load.

In the network logs I can see that Firefox tries to connect to my mobile provider's proxy using port 80 instead of 8001. (See attached screenshot)

All other apps connect to the proxy on port 8001.

Expected results:

Firefox should use port 8001 for the proxy as detected by Android.

Comment 1

[jackyzy823]

Since my mobile provider do not use proxy. So i can only create a new APN profile with a random pseudo proxy like "Proxy: 1.0.0.1 , Port 32766".

However i cannot observe the problem , i use PCAPdroid to monitor the traffic, it show firefox connect with TCP 1.0.0.1 port 32766. So i assume Firefox working correctly.

I'm using Firefox Beta 118.0b8.

Comment 2

[reconman]

The bug could be specific to Android 13 or to OnePlus.

Another OnePlus user reported the same issue in the support forum: https://support.mozilla.org/en-US/questions/1423533#answer-1603607

I tested a custom APN and it showed similar behavior, Chrome used the self-defined proxy port while Firefox did not.

Tell me if you need me to run any commands for further diagnosis. I can also run them with root privileges.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:jonalmeida, could you have a look please?

For more information, please visit BugBot documentation.

Comment 4

[Jonathan Almeida [:jonalmeida]]

Moving to the Core HTTP component to see if the triage owner there has any recommendations for what kind of useful logging from comment 2 might help.

Comment 5

[Valentin Gosu [:valentin] (he/him)]

So, if I understand things correctly, the proxy information is passed into Gecko from GeckoAppShell::getProxyForURI which looks at system properties to lookupProxy
I'd start there to confirm that we get the correct value from the system.

Also note the previous comment.

(In reply to reconman from comment #2)

The bug could be specific to Android 13 or to OnePlus.

Another OnePlus user reported the same issue in the support forum: https://support.mozilla.org/en-US/questions/1423533#answer-1603607

Comment 6

[Renaud Lehoux]

I think we found the source of the issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1858377#c1

Comment 7

[Valentin Gosu [:valentin] (he/him)]

Thanks!