Closed
Bug 2056606
Opened 1 month ago
Closed 1 month ago
Add live support for policy WebsiteFilter
Categories
(Enterprise Products :: Firefox, enhancement, P1)
Enterprise Products
Firefox
Tracking
(Not tracked)
VERIFIED
FIXED
MVP
People
(Reporter: janika, Assigned: janika)
References
Details
Attachments
(1 file)
No description provided.
| Assignee | ||
Updated•1 month ago
|
| Assignee | ||
Updated•1 month ago
|
Type: task → enhancement
Updated•1 month ago
|
tracking-firefox154:
? → ---
tracking-firefox155:
? → ---
Comment 1•1 month ago
|
||
| Assignee | ||
Updated•1 month ago
|
Assignee: nobody → jneuberger
Comment 2•1 month ago
|
||
Authored by https://github.com/1rneh
https://github.com/mozilla/enterprise-firefox/commit/5f0a2ecb12767fdf0a22897dd0ef0ba90bdbc591
[enterprise-main] Bug 2056606 - Add live support for policy WebsiteFilter (#1197)
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
| Assignee | ||
Comment 3•1 month ago
•
|
||
Test Plan
Use https://example.com/ and https://example.org/ as test sites, one in each tab.
How to verify the result of each test case
about:policies#active— listsWebsiteFilterand its currentBlock/Exceptionsvalue.- Navigation indicator — on a site the policy blocks, navigating to it shows the " Access to this site is restricted" error page (see
about:neterror?e=blockedByPolicyEnterprise); on a site the policy does not block, the page loads normally. Reload the tab after each policy change to observe it.
At every step, confirm the navigation result reflects the change after a reload, without restarting the browser.
Use two tabs throughout: one on https://example.com, one on https://example.org.
Test cases
1. Apply
- Confirm
WebsiteFilteris not active and both example.com and example.org load normally. - In the console, set
WebsiteFilter:
{
"Block": ["*://*.example.com/*"]
}
Expected:
- In
about:policies#active:WebsiteFilterlisted with the value above. - example.com shows the blocked error page; example.org still loads normally.
2. Update I
- Change
Blockto example.org:
{
"Block": ["*://*.example.org/*"]
}
Expected:
- In
about:policies#active:WebsiteFilterupdated to block example.org. - example.com loads normally again and example.org now shows the blocked error page.
3. Update II
- Switch to an allowlist by blocking everything except example.org via
Exceptions:
{
"Block": ["<all_urls>"],
"Exceptions": ["*://*.example.org/*"]
}
Expected:
- In
about:policies#active:WebsiteFilterupdated to the block-all + exception value. - The policy now applies to every site except example.org: example.com shows the blocked error page and example.org loads normally.
4. Update III
- Set
Blockback to example.com:
{
"Block": ["*://*.example.com/*"]
}
- Navigate to a URL that HTTP-redirects (30x) into example.com — e.g.
https://httpbin.org/redirect-to?url=https://example.com/.
Expected:
- In
about:policies#active:WebsiteFilterupdated to block example.com. - The redirecting URL lands on the blocked error page.
5. Remove
- Remove
WebsiteFilterfrom the policy set.
Expected:
- In
about:policies#active:WebsiteFilterno longer listed. - example.com (and every other site) loads normally again, including the redirecting URL from the previous step.
Flags: qe-verify+
Comment 4•26 days ago
•
|
||
Verified fixed using FxE 155.0a1 (20260807105404) on Windows 10, MacOS 26 and Ubuntu 24.
Test-case added here.
Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in
before you can comment on or make changes to this bug.
Description
•