This means it won't work on a VPN, isn't suitable for any situation where the other origin is returning sensitive or protected data, and allows hacks from any of those proxy sites should any of them choose to inject JS into the content.
The control needs to allow the proxies to be specified and overwritten.
In addition the documentation needs to make clear that these external proxies are being used and the consequences: only GET works, cookies are not included, unknown 3rd party gets chance to copy the content and add whatever they want before your users run it.
This sends requests by one of 3 external proxies: https://github.com/niutech/x-frame-bypass/blob/855835ec48f92bfc825a88284b17218cb1867f7f/x-frame-bypass.js#L68-L70
This means it won't work on a VPN, isn't suitable for any situation where the other origin is returning sensitive or protected data, and allows hacks from any of those proxy sites should any of them choose to inject JS into the content.
The control needs to allow the proxies to be specified and overwritten.
In addition the documentation needs to make clear that these external proxies are being used and the consequences: only
GET
works, cookies are not included, unknown 3rd party gets chance to copy the content and add whatever they want before your users run it.