Currently “Exact” URI match includes query strings and fragment identifiers.
This behavior causes unnecessary mismatch when the base URI is the same but query parameters or fragments differ.
Please consider adding an additional matching option where autofill triggers only when the base URI (scheme, host, port, and path) matches exactly.
@fg3hfpav Welcome to the forum!
Wouldn’t that be what the “starts with” matching option already can do?
Hello, @Nail1684! Thank you for the welcome.
The “starts with” option behaves differently from “Exact” (it also matches subpaths) and cannot be conveniently registered using “Fill and save.”
To function properly with it, the query and fragment parts must be manually removed one by one.
“Exact” and “Starts With” both match subpaths (if subpaths are included in the stored URI). So I don’t understand what you are stating above, and would appreciate a clarification of what you meant.
As noted by @Nail1684, you can already do this using “Starts With”. Alternatively, you could do it using “Regular Expression”. In both cases, you would have to edit the stored URI to make the matching work as intended.
It seems that the feature you are actually proposing is some mechanism to avoid having to edit the URI strings that are stored using “Fill and Save”. This could either be a modified “Starts With” method that automatically ignores query or fragment strings at the end of the stored URI, or a modified “Fill and Save” function that automatically strips query or fragment strings from the end of the stored URI.