You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
70% of the traffic to our Ember app comes through an iframe. Since we started using Ember Front End Builds (which we love!) we are hitting a this error:
Refused to display 'https://www.hotdoc.com.au/book-appointment/harbourtown-medical-centre' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.
Can we set the X-Frame-Options of the headers to allow cross domain iframe embedding?
What we used to do with our old Ember app, which was embedded in Rails was adding the following to the relevant controller:
# Allow access within an iframe
response.headers.delete 'X-Frame-Options'
Or:
# Allow access within an iframe
response.headers['X-Frame-Options'] = 'ALLOW'
Is that also possible with Ember Front End Builds?
PS: Keep up the great work! Ember Front End Builds is the single best process improvement we introduced to our Ember app.
The text was updated successfully, but these errors were encountered:
@ryanto looks like we need to add the ability for users to subclass the bests controller so they can alter the response before it goes out. What do you think?
Hi Tedconf,
70% of the traffic to our Ember app comes through an iframe. Since we started using Ember Front End Builds (which we love!) we are hitting a this error:
Refused to display 'https://www.hotdoc.com.au/book-appointment/harbourtown-medical-centre' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.
Can we set the X-Frame-Options of the headers to allow cross domain iframe embedding?
What we used to do with our old Ember app, which was embedded in Rails was adding the following to the relevant controller:
Or:
Is that also possible with Ember Front End Builds?
PS: Keep up the great work! Ember Front End Builds is the single best process improvement we introduced to our Ember app.
The text was updated successfully, but these errors were encountered: