You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably a kind of niche thing, but some sites specifically want non-encoded strings. For example, First.org's CVSS calculator wants results formatted like so: https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, no encoding applied to anything after the hash. Thus trying to add a bang for https://first.org/cvss/calculator/3.1#%s is broken.
Is it possible / reasonable to add a config option for "encode / don't encode queries from this bang"?
The text was updated successfully, but these errors were encountered:
Probably a kind of niche thing, but some sites specifically want non-encoded strings. For example, First.org's CVSS calculator wants results formatted like so:
https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
, no encoding applied to anything after the hash. Thus trying to add a bang forhttps://first.org/cvss/calculator/3.1#%s
is broken.Is it possible / reasonable to add a config option for "encode / don't encode queries from this bang"?
The text was updated successfully, but these errors were encountered: