|
Instead of trying to reverse engineer the javascript to do the decryption, would it be possible to leverage something like webdriverio to drive Chrome? This would allow the browser to render the page properly and then the recipe would just pull the rendered DOM which has already been decrypted. Main advantage here is if the decryption javascript changed in the future it wouldn't matter - at the end of the day the content has to render in a browser.
No idea if it's possible for the recipe to use something like webdriverio so might be barking up the wrong tree.
|