Hi Oana, Here is the reason why sometimes the site(phishing.html) doesn't show a warning: In the test.html, there are two iframes 1. "https://testsafebrowsing.appspot.com/s/phishing.html" 2. "https://itisatrap.org/firefox/its-a-trap.html" The itisatrap.org site always shows a warning because the URL is hard-coded in the codebase for test purpose, no matter an update is triggered our not. The reason that the site(phishing.html) still doesn't show a warning after triggering an update manually via about:url-classifier, is that the webpage is cached by necko. So when you refresh the webpage, it doesn't send any HTTP request, it just reuses the content. If you are ok with this, I think we can close this bug.
Bug 1535289 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hi Oana, Here is the reason why sometimes the site(phishing.html) doesn't show a warning: In the test.html, there are two iframes 1. "https://testsafebrowsing.appspot.com/s/phishing.html" 2. "https://itisatrap.org/firefox/its-a-trap.html" The itisatrap.org site always shows a warning because the URL is hard-coded in the codebase for test purpose, no matter an update is triggered or not. The reason that the site(phishing.html) still doesn't show a warning after triggering an update manually via about:url-classifier, is that the webpage is cached by necko. So when you refresh the webpage, it doesn't send any HTTP request, it just reuses the content. If you are ok with this, I think we can close this bug.