Feature request: When displaying a blocked URL, show decoded query string values in a table.

[hydra]

Prerequisites

• This is not a support issue or a question. For support, questions, or help, visit /r/uBlockOrigin.
• I performed a cursory search of the issue tracker to avoid opening a duplicate issue.
  normal behavior.

Description

Many blocked URLS contain redirects, such as those found in emails. it would be helpful if when the blocked URL is displayed that the values of each query string key/value pair were decoded and displayed in a table.

for bonus points, for each value in the table, ideally:

• if the value is a URL make it clickable.
• add a small 'copy to clipboard' button with icon to allow the value to be copied to the clipboard.
• show the detected encoding method.
• allow the user to try decond with an alternative common decoder if the decoder can't be autodetected, via a dropdown/combobox/popup.

e.g. modify this area:

I feel this would drastically improve the usability of the redirect warning page.

Maintainers: I could not find an issue tracker item for feature requests, so I entered this as a bug report, please feel free to move/convert the issue or let me know where to open one.

[stephenhawk8054]

What is the encoding method in your screenshot? And what are the output results from those parameters?

[gorhill]

I can't investigate what I can't reproduce. I can't solve what I can't investigate. A screenshot alone is not a "step to reproduce". Without minimal basic information to reproduce, this request is unactionable.

[krystian3w]

Probably in f is a URL encoded in "base64".

Unfortunately this is not handled by the free OCR or me transcribing character by character (dyslexia does not make it easier), I get gibberish with non-printing characters:

0001ArcX1fqz7LLT9embqFaAF3Touc6WD8dfKKLkIssyycwTe77yBLAWQYo1T3U_rAfWZeInWA6Vqk7Ag726VZksiNBXo2qJ8nXHki3WV5Hy0CKAoNwFVB0fiW6SCjBhqWsgvSEELTPXKQNzWJIwt-HRuwri8VyRnXflE1GLS4=

So it will probably be difficult to make an if-then which detects the likely encoding based on the absence of non-printing characters (e.g. no looping with different encodings).

The field that we will be redirected to some URL is already there when we have a match with urlskip=.