Open Bug 1468702 Opened 6 years ago Updated 2 years ago

Remote Autoconfig with "autoadmin.failover_to_cached" set to False is not marking the browser offline

Categories

(Core :: AutoConfig (Mission Control Desktop), defect, P5)

62 Branch
defect

Tracking

()

Tracking Status
firefox62 --- affected

People

(Reporter: roxana.leitan, Assigned: mkaply)

References

(Depends on 1 open bug)

Details

Attachments

(1 file)

Attached image remote autoconfig.png
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0
Build ID: 20180613220131

[Affected versions]:
Nightly 62.0a1

[Affected Platforms]:
Windows 10 x64, Mac OS X 10.13

[Preconditions]:
1.Create a file named autoconfig.js in the location: 
C:\Program Files\Mozilla Firefox\defaults\pref
and add the following text to it: 
"pref("general.config.filename", "firefox.cfg");
pref("general.config.obscure_value", 0);
pref("general.config.sandbox_enabled", true);"

2.Create a file named autoadmin.js on a remote location and add the following text to it: 
//
pref("autoadmin.failover_to_cached", false);"

3.Create a file named firefox.cfg in the location: 
C:\Program Files\Firefox Nightly
and add the following text in it:
"//
lockPref("autoadmin.global_config_url","http://yourdomain.com/autoadmin.js");"

[Steps to reproduce]:
1.Launch Firefox
2.Go to about:config and search for "autoadmin.failover_to_cached"
3.Go to about:support ->Profile folder and search for failover.jsc file

[Expected result]:
The "autoadmin.failover_to_cached" pref status should be "modified" and the value should be "false"
The failover.jsc file should be created with the same content as autoadmin.js
The browser should be marked as offline (Menu-> File-> Work Offline option should be checked and greyed out)
After Firefox reads the cached file(failover.jsc), the preference should be locked 

[Actual result]:
The "autoadmin.failover_to_cached" pref status is "modified" with false value
The failover.jsc file is created
The browser is not marked offline and the user can go online

[Note]:
There's no difference if I set "autoadmin.failover_to_cached" pref on True
The behaviour persists after restart browser or if I added "autoadmin.offline_failover" preference set to True in autoadmin.js file
After the remote connection is closed and the browser is restarted, the browser is marked as offline ((Menu-> File-> Work Offline option is checked and greyed out) and the user can't go online, but the preference is not locked.
Does it work if you set autoadmin.failover_to_cached in firefox.cfg?

I think all the autoadmin prefs need to be set in the CFG file.
It doesn't work with "autoadmin.failover_to_cached" in firefox.cfg.

The browser is marked offline only if the remote connection is closed and the browser is restarted; the preference is not locked.
(In reply to roxana.leitan@softvision.ro from comment #3)
> It doesn't work with "autoadmin.failover_to_cached" in firefox.cfg.
> 
> The browser is marked offline only if the remote connection is closed and
> the browser is restarted; the preference is not locked.

If I open FF with a new profile, the browser is in offline mode(greyed out)(with remote connection closed)
First off, any autoadmin prefs should be set in the CFG file. They can't be set in the remote file because they are needed before the connection happens.

The best way to test autoadmin.failover_to_cached is with a new profile.

If you have autoadmin.failover_to_cached set to false and you create a new profile, but the autoadmin.global_config_url is an invalid URL, the browser will start but will be locked in offline mode.

This also happens if you ever change the global config URL to an invalid URL.

autoadmin.failover_to_cached set to false means "If you can't actually retrieve the URL for the autoconfig, go offline even if there is a cached file"

That's why it has to be in the CFG file and not in the remote file.

If you set it to true, it will use the cache if it is available, but it does not stay offline if it is not available.
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: