When i-Vault records the URL of what page from which it has recorded data entered into the fields on that page, it should NOT also include the parameters in the URL for that page. The problem is that the parameters could be different every time that page is visited, so i-Vault will record a NEW page on every visit although it is the SAME page.
Do not record:
http://<somedomain>/<somepath>?<someparameters>
But instead just record:
http://<somedomain>/<somepath>
That is, record everything up but not including at or after the question mark used to delimit any parameters used within the URL. Then i-Vault can accurately determine that it is revisiting the same page regardless of what parameters are used or their values.
An an example of why including the parameters is a problem, go visit the SpamPal forums at:
http://www.spampalforums.orgTake a look at the "Login" link and notice that it goes to:
http://www.spampalforums.org/phpBB2/login.php?sid=<somerandomnumber>
Each and every time you visit that page, the value of the sid object will be different. The only thing that i-Vault needs to know to recognize the login page is everything up to but not including the question mark and the parameters after it. Otherwise what happens is that i-Vault will record yet another entry for what it thinks is a different web page - and you will NEVER get it to pre-fill in the login credentials.
I haven't a clue why the developers of i-Vault were so lazy as to not bother parsing the URL to truncate it on after after the question mark character. The parameters may be important in a link that navigates *to* a page but once AT that page then they are unneeded. Could be they are used to provide default values for controls on that page but then the purpose of i-Vault is to enter its own recorded values to insert into those controls (and overwrite any that may already be there).