-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add rules for bouncers with encoded JSON blobs #880
Comments
In this case, we need to:
Here's what the JSON blob looks like:
The |
Just a though, but initially when i spec'ed the debounce feature, i described a pipeline of different actions that could be applied to a URL to extract the destination URL. Things like "apply regex", "base64 decode the buffer", "extract JSON key", "extra query param key" and "extract path segment". If we're going to start targeting these more sophisticated cases (which i think is a great idea) maybe it'd be good to revisit that original idea, so that we can have a smaller number of composable actions, instead of a large number of single-and-few-use actions? |
This was the original proposal in case its of interest:
|
Base64 + JSON: https://www.emjcd.com/links-i/?d=eyJzdXJmZXIiOiIxMDA3MDQyOTIzNzA2MDQ1MTg6SU91QlNqanZBMHZjIiwibGFzdENsaWNrTmFtZSI6IkxDTEsiLCJsYXN0Q2xpY2tWYWx1ZSI6ImNqbyF3dnhqLWEwZThkazctd3ppZy1kc25oanZhLWdoaWktbG5jbWJuei13NXRlLWRzNzNwbmUtdzc3Mi12MDRjcTNkIiwiZGVzdGluYXRpb25VcmwiOiJodHRwczovL3d3dy5jYXJoYXJ0dC5jb20vcHJvZHVjdC84MDE5NjYvZm9yY2UtcHJvLTM1bC1iYWNrcGFjayIsInNpZCI6Ii0tLSIsInR5cGUiOiJkbGciLCJwaWQiOjEwMDIyMzY2NCwiZXZlbnRJZCI6IjUwNjYzNTRiNGU0OTExZWM4MzY4MDNkZTBhMWMwZTBiIiwiY2pTZXNzaW9uIjoiYjMyZDQzYjItNjVkMi00NTZiLThjMmItZTY2NmExN2I4OTY0IiwibG95YWx0eUV4cGlyYXRpb24iOjAsInJlZGlyZWN0ZWRUb0xpdmVyYW1wIjpmYWxzZSwiY2pDb25zZW50RW51bSI6Ik5FVkVSX0FTS0VEIn0%3D
What needs to be done:
d
parameter from the query string.destinationURL
in the resulting JSON blob.Here's what the JSON blob looks like:
The text was updated successfully, but these errors were encountered: