Disable Proxy settings don't bypass Window settings
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: vcastelblanque, Unassigned)
Details
Attachments
(7 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:97.0) Gecko/20100101 Firefox/97.0
Steps to reproduce:
The system is configured to use a proxy. In Firefox, I go to proxy settings options and click on the option "no proxy" but it doesn't work. Proxy is still working and I cannot access to the urls that I cannot access with other explorer, configured to use the windows proxy.
Firefox
I made the same with Firefox developer edition version 90.0b1 (64-bit) and it works perfectly.
Note: I prevent that other programs change the file fp_mozilla_F1E.cfg bercause I have administrator profile
Actual results:
Proxy is still active in Firefox and i cannot visit some pages that I should be able to visit without proxy.
Expected results:
Firefox should bypass windows settings, avoid the use of the proxy and go directly to internet.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Settings UI' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•3 years ago
|
Not able to reproduce with UA: Mozilla/5.0 (windows NT 10.0; Win64; x64 rv:107.0) Gecko/20100101 Firefox/107.0 or v103. Though I didn't make any modifications to the cfg/admin profile.
- Is this still occurring on newer versions 97+ (non-developer)?
- I'm not familiar with the fp_mozilla_F1E.cfg. Does bug still happen without your admin profile changes protecting the file? If not, what is the file for and where is it and can you provide steps to create similar one?
- Can you provide http logs. You may want to email to necko@mozilla.com if there are personal info contents.
Yes, I've tested several versions with the same result.
The file locks the proxy settings configuration in firefox. I need to unlock it in order de change to "no proxy" and then prevent that the program "forcepoint one endpoint" change it again (i only change to a read only file). The file is in firefox directory.
If you restart the browser after your "no proxy" configuration, does firefox still use the system proxy settings?
Are you able to provide a minimal config file to replicate?
If I check in Firefox option, the configuration is in "Sin Proxy" (without proxy) as you can see in "Proxy_Settings_configuration.PNG". But if I try to go to some pages, I can see that the proxy is working.
fp_mozilla_F1E.cfg file contanis this to lock the configuration of proxy in Firefox
//
lockPref("network.proxy.type", 5);
lockPref("network.proxy.no_proxies_on", "");
To unlock, I delete the content, save the file and change rights to read only.
Tell me which other files do you need and I will try to sent to you .
I checked also version 99 and it works. I wil try to install other versions in order to know exactly, from which version don't work.
Ok, the lock doesn't seem related because you are able to change at least the UI to "No Proxy".
Thanks for looking into the version, it may also be helpful if we can get some http logs of your reqests made after switching to "No proxy".
| Reporter | ||
Comment 10•3 years ago
|
||
Hello,
sorry for being late. Here you have the log file. I tryed with Http and Https, becuses with Https, I allways have a SSL_ERROR_RX_RECORD_TOO_LONG, but in my opinion it's problem of the proxy, and not a Firefox problem or is another problem that is not part of this BUG.
In the other version, i see the page, but in that i see the meesage of the proxy "The Web site you requested is blocked by your organization."
Comment 11•3 years ago
|
||
The severity field is not set for this bug.
:smayya, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Comment 12•3 years ago
|
||
This looks like not a networking bug, since the http log shows that there is no proxy used for all http requests.
Since you said Firefox worked with the old version before, maybe you can try mozregression to help us figure out the problem?
Thanks.
| Reporter | ||
Comment 13•3 years ago
|
||
I will try to use mozregression, but I'm not sure if I could do. Let me try
Comment 14•3 years ago
|
||
I'll keep the ni flag ot indicate that this bug is still waiting for more information. Please clear it when you have more information.
| Reporter | ||
Comment 15•3 years ago
|
||
I was trying to use the tool, but I cannot. Let me try again but I'm not sure to can.
| Reporter | ||
Comment 16•3 years ago
|
||
The thing is, why is in UNCONFIRMED when is confirmed?
Comment 17•3 years ago
|
||
I just checked again the log that you provided. It shows that Firefox didn't try to connect to the proxy at all.
So, I think this might be a misconfiguration or there is a mitm proxy somewhere.
Anyway, I think this is not a Firefox issue, so I'll close this. Feel free to reopen if you have more information to provide. Thanks.
| Reporter | ||
Comment 18•2 years ago
|
||
So, is it not important the evidences about that when I said that with several older version works, and not in the new one.?
I was trying to use mozregression but i don't know how to avoid the use of the proxy with this application, so always I have the same result (the proxy response). If you can say me how to do it, I probably can retry again.
But I will include new logs:
- Version 108 ((108.0b2 (64-bit))log.txt-main.14472.moz_log, don't work)
- Version 110 ((110.0b1 (64-bit))log.txt-main.3572.moz_log, don't work),
- Version 90 ((90.0b1 (64-bit))log.txt-main.16920.moz_log, work),
- Version 99 ((99.0b1 (64-bit))log.txt-main.11276.moz_log, work).
Each of one has screen capture of what I see in firefox.
I hope it help.
| Reporter | ||
Comment 19•2 years ago
|
||
Comment 20•2 years ago
|
||
I've looked all logs and I found there was no proxy used at all. I also can't find any network issues from the logs.
Maybe the reason is that the server (or the mitm proxy) doesn't accept Firefox's UA string.
So, what happens if you use Firefox version 110 and change the UA string to Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:99.0) Gecko/20100101 Firefox/99.0?
| Reporter | ||
Comment 21•2 years ago
|
||
I will try and come back with the results.
| Reporter | ||
Comment 22•2 years ago
|
||
| Reporter | ||
Comment 23•2 years ago
|
||
| Reporter | ||
Comment 24•2 years ago
|
||
| Reporter | ||
Comment 25•2 years ago
|
||
Sorry for being late.
I've made the changes and have the same result. The proxy is working even I have disabled it. I've attached the log log.txt-main.16372.moz_log.
I've also made some captures with Whireshark. and I've realised, that the ip used with the GET function is not the same.
In "captura_whireshark_firefox_099.PNG " you can see that that the IP used is 217.22.17.248, but in "captura_whireshark_firefox_111.PNG" you can see that the IP used is 85.115.44.180, which is the one used always when the proxy is configured, even it is not configured.
Comment 26•2 years ago
|
||
It looks like the log log.txt-main.16372.moz_log is not complete, since I can't see Firefox making a CONNECT request inside the log.
I also can't find the ip 85.115.44.180 in the log. If Firefox tried to connect to 85.115.44.180, we should see that.
Sorry that I'd like to ask you to record the http log again, since the bug might occur during startup. Please see the instructions here.
Also, could you also add proxy:5 to the MOZ_LOG env?
Thanks!
| Reporter | ||
Comment 27•2 years ago
|
||
how can i add this proxy:5 to the moz_log?
| Reporter | ||
Comment 28•2 years ago
|
||
| Reporter | ||
Comment 29•2 years ago
|
||
You have attached the file log.txt.child.rar.
I've executed this:
set MOZ_LOG=timestamp,rotate:200,nsHttp:5,cache2:5,nsSocketTransport:5,nsHostResolver:5,proxy:5
tell me if there is something mising
Comment 31•2 years ago
|
||
(In reply to deltodo from comment #30)
Any news?
No. The log still shows that Firefox didn't use proxy at all. I assume there might be a transparent proxy between Firefox and the server and there is nothing we can do about it.
| Reporter | ||
Comment 32•2 years ago
|
||
I don't know if ther is a transparent proxy or not, but the fact is that with a older version works and with the new don't work.
So I can guess that there is something that is not shown in the logs that make that even you don't have the proxy configured (at least in the known place that have to be configured) it use the proxy.
But I do not insist any more..
Description
•