We frequently visit sites that use long query strings. Some of these strings are unique and session-specific, and the server will never allow them to be used again. Other… (xem thêm)
We frequently visit sites that use long query strings. Some of these strings are unique and session-specific, and the server will never allow them to be used again. Other query string variables are used for session-specific navigation, like a page number or a record ID, and we may never have interest in trying to get back to that exact same spot within an application, but we might want to save some higher-level entry point. As a simple example, look at your history and see how many entries there are for 'www.google.com/url'.
To reduce the size of my history, I'd like to filter what gets logged. Actually I don't mind "History" for history's sake as a record of places we've actually been. The problem is that the same database is used for autotype and other purposes. The current implementation is not ideal for going back and visiting "applications" versus "specific web addresses". Maybe it's better to state that History should track URI's but when we are navigating back through History to go back to a specific page we're more interested in a less-specific URL. Using Google as an example again, it's OK for History to record the fact that I've visited a hundred Google search pages, or page 2,3,4 for a specific search, but ultimately I might only want to save the part of the query string that is relevant to a specific search. The next time I go back to some page there might not be a page 4, so if I'm going through history again for the purpose of revisiting pages, I just want to see page 1 of the results.
Can anyone recommend a plugin that allows regex filtering of history, or recording of page visits into a different database in addition to Firefox History? From there of course it would be convenient to filter that data by time and otherwise, just like History.
From a developer perspective, History gets written to a specific database/file - can someone tell us exactly which file and format that is? I might be able to write a post-processor that filters out underable records.
Is there a better approach to managing history?
Is History just an automatic Bookmark, meaning I should be looking for a bookmark manager for this?
Or maybe we should do a mass copy of History into a dedicated Bookmark folder, manipulate records there, and use that for back-navigation?
Time to create an Enhancement request?
Should I write a plugin? :)