1338079 - (about:url-classifier) [meta] Exposing troubleshooting information for Safe Browsing via about:url-classifier

Status: NEW

(Toolkit :: Safe Browsing, enhancement, P3)

Description

[François Marier [:francois]]

In order to simplify testing and debugging, we should create a new about:url-classifier page.

It would contain a these sections:

1. Cache
2. Database
3. Providers
4. Lookup

The first section (cache) would display the size of the lookup cache for each table and have a button to clear that cache.

The second section (database) would show the number of entries in each table and have a button to clear the database from memory and reload it from disk.

The third section (providers) would show the following information for each provider:

- time of last update
- last update return status (e.g. 200, 503)

and have a button to force an update for just that provider.

The last section would have a text box to allow us to lookup a URL in the local database (possibly triggering gethash calls too). It would display (as text) a log of what happened internally during that lookup. For example:

prefix was found in table goog-malware-proto
full hash was not found
negative cache expired for that prefix
requesting full hash
full hash found in result
found a match for malware.example.com/

This new about:url-classifier page should be linked from about:about.

Comment 1

[Ethan Tseng [:ethan]]

This is a wonderful idea!
Looking forward to seeing it being rolled out.

Comment 2

[Dimi Lee [:dimi]]

I'll start with "Update" function first, since there are lot of features we want to do in this about page, maybe this bug should be a meta bug.

Comment 3

[Ethan Tseng [:ethan]]

(In reply to Dimi Lee[:dimi][:dlee] from comment #2)
> I'll start with "Update" function first, since there are lot of features we
> want to do in this about page, maybe this bug should be a meta bug.

Agree.
The ability to trigger update is especially useful for QA engineers who perform stress or performance tests.

Let's turn this into a meta bug and file sub-bugs accordingly.

Comment 4

[Dimi Lee [:dimi]]

Attachment: WIP patch

Comment 5

[Dimi Lee [:dimi]]

(In reply to Ethan Tseng [:ethan] from comment #3)
> (In reply to Dimi Lee[:dimi][:dlee] from comment #2)
> > I'll start with "Update" function first, since there are lot of features we
> > want to do in this about page, maybe this bug should be a meta bug.
> 
> Agree.
> The ability to trigger update is especially useful for QA engineers who
> perform stress or performance tests.
> 
> Let's turn this into a meta bug and file sub-bugs accordingly.

Ah, just saw your comment after pushing a WIP.
I'll push my WIP to bug 1348253.

Comment 6

[Dimi Lee [:dimi]]

deassign myself since this is a metabug.
I will file bug for different about:url-classifier functions and work on them.