Pass variables to a custom block page
launched
Jonathan Hozeska
Please add the ability to pass simple variables to a custom block page.
For example:
Offending IP address/URL
Category of offending IP/URL
IP of host making the request
Username (if available) of the host making the request if available.
By appending variables to the end of the custom Block page redirect URL the block page can be dynamically updated to give the end user more details on why the request was blocked. It can able be used to programmatically interact with RMM/PSA tools.
Cisco Umbrella has had this this future for their custom block page redirects for several years.
Nick Saunders
launched
Released on Aug 17, 2023 - https://dnsfilter.canny.io/changelog/august-17-2023-app-release
Matthew
Nick Saunders: Not seeing any change. Does it take a bit to roll out to customers?
Nick Saunders
Matthew: Hi Matthew, yes it looks like there's a delay on the description text showing up - sorry about that! You should be seeing the parameters passed on a redirect now though if want to test and confirm.
Matthew
Nick Saunders: Oh, hey, while I have you, these are still separated from the URL by a #. So these aren't usable by whatever app customers 302 the request to
Nick Saunders
Matthew: Thanks for the quick feedback, certainly not our intention - we'll get it fixed ASAP.
Nick Saunders
Matthew: Hey Matthew, we made a change that should support ? instead of # in the URL - you just need to add a ? to the end of URL you enter for the Redirect field. Without that you'll still see the #. We have some customers using the parameters on static pages that work better with #, but we want to support both use cases. We'll have these details added to our help docs soon. Let me know if it's not working for you. Thanks!
Matthew
Nick Saunders: Great! Yep, looks like it's accepting it just fine. Thank you!
Jonathan Hozeska
With my Cisco implementation I pass the variables through to a few different APIs to return more details on why the destination is blocked. It makes for a much calmer discussion with the end user when they know why we are blocking a site instead of the cold default messages of 'the site is blocked because we said so.' And of course, we log it all and can trigger e-mails or automation to track abuse or create billable tickets.
Giuseppe
Hello, this is really needed. Also other tools less expensive have this possibility.
Matthew
This! Passing even the domain would be great, right now it's appended with # and not fetch-able in the page. Support told me I could use JS to pull that data... but using "?" would allow for a lot more extensibility and automation.