Now when password is saved, full url is attached. That includes possible token part (e. g. password reset urls, email confirmations, etc)
Add default option to save only main url and ignore anything after domain.
Now when password is saved, full url is attached. That includes possible token part (e. g. password reset urls, email confirmations, etc)
Add default option to save only main url and ignore anything after domain.
Could you please provide some additional explanation of your concerns with the current implementation? Currently, the full string is saved, but only the host part of the URL (www.example.com
) is displayed (unless the login item is being edited), and only the base domain (example.com
) is used for URI match detection (unless the default settings have been changed). Thus, in most cases, the unused part of the saved URL string should not affect the user experience in any negative way. In your use-case, why is it important for the remaining part of the stored URL string to be deleted altogether?
When opening site from item, it opens full url, leading wrong page (error page, registration form etc.)
Also, editing url is painful with sometimes very lengthy url (like email confirmation link that bitwarden decided to save) especially when latest update introduced
this bug.
Thanks for providing additional explanation.
FYI, the bug that you mentioned should be fixed in the next release.
Another work-around is to simply save the desired launch page as an additional URI, and then drag that URI to be the first in the URI list.