Skip to content
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

Work around for pages that can't do frames? #64

Open
Kezzsim opened this issue Aug 6, 2016 · 2 comments
Open

Work around for pages that can't do frames? #64

Kezzsim opened this issue Aug 6, 2016 · 2 comments

Comments

@Kezzsim
Copy link

Kezzsim commented Aug 6, 2016

So back when I used to use Xibo (which I had to stop using because the client had a reallly bad memory leak) I remember I was able to insert wholesale embed code into my sign layouts as a workaround for lack of frame support. Is there any way I could drop embed code in the url space of this app to get framed objects to display? Or some sort of 3rd party workaround...

@Kezzsim Kezzsim changed the title npm start gets stuck at creating design doc... Grey screen of death Aug 6, 2016
@Kezzsim Kezzsim changed the title Grey screen of death Work around for pages that can't do frames? Aug 6, 2016
@nadav-dav
Copy link

you could create a small proxy the removes the X-FRAME header.

checkout https://www.npmjs.com/package/http-proxy#setup-a-stand-alone-proxy-server-with-proxy-request-header-re-writing

@superhawk610
Copy link

I just published multicast, Greenscreen's spiritual successor for the new Castv2 API via mDNS. We're continuing active development there, and ran into the same issue (see issue #1). What are the moral/professional implications of stripping a header?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants