# تضمين تطبيق ويب مستضاف على AppEngine عبر IFRAME

**URL:** <https://meta.discourse.org/t/embedding-an-appengine-hosted-web-app-via-iframe/87280>\
**Category:** Product Support\
**Created:** [11 مايو 2018، 4:54م UTC](https://meta.discourse.org/t/embedding-an-appengine-hosted-web-app-via-iframe/87280 "2018-05-11T16:54:48Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [12 مايو 2018، 12:18ص UTC](https://meta.discourse.org/t/embedding-an-appengine-hosted-web-app-via-iframe/87280/3 "2018-05-12T00:18:05Z")

</div>

This doesn’t look like a Discourse problem. If you fix the URL you’re embedding to not cause a 307, everything will probably work a lot better. Interestingly, the “307 Internal Redirect” is reportedly issued when Chrome is asked to load a HTTP resource for a domain for which it has an HSTS policy active. However, in your case the headers suggest that it’s already a HTTPS URL, so presumably there’s also other cases where Chrome does the same thing. Either way, though, this isn’t a problem with Discourse, it’s a browser/embedded site problem.

---

_[View the full topic](https://meta.discourse.org/t/embedding-an-appengine-hosted-web-app-via-iframe/87280)._