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.
mpalmer
(Matt Palmer)
3
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Cannot get embedding to work | 11 | 2830 | August 31, 2021 | |
| Discourse embed blocked on "Loading Discussion..." | 5 | 2715 | October 13, 2015 | |
| Discourse not shown in iframe | 30 | 8992 | April 26, 2021 | |
| How to run the discourse in Iframe? | 1 | 431 | April 17, 2023 | |
| Making discourseEmbedURL match expected topic requirements | 5 | 1695 | August 16, 2016 |