Replies: 1 comment 2 replies
-
We need this for cross-origin iframes, to limit the access of custom JS to Livebook. The issue is that for cross origin iframes over HTTPS, you need to host a page on a separate port over HTTPS, which you would have to provide. That’s hard to do by default. So we either provide a broken version over HTTPS or we go with the current approach. If you have alternatives in mind, please let us know. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For enabling HTTPs, why must Livebook connect to https://livebookusercontent.com/? Why can't the content be hosted locally like with http? Other than modifying the code, is there any way to disable this functionality?
EDIT:
LIVEBOOK_IFRAME_URL - sets the URL that Livebook loads iframes from. By default iframes are loaded from local LIVEBOOK_IFRAME_PORT when accessing Livebook over http:// and from https://livebookusercontent.com/ when accessing over https://.
Ah, so you can override it by setting LIVEBOOK_IFRAME_URL. Still, I think this should be something that is opt-in rather than opt-out.
Beta Was this translation helpful? Give feedback.
All reactions