# Did onebox change? They're not showing for my main site any longer

**URL:** <https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901>\
**Category:** Support\
**Created:** [2017年六月4日 11:30 UTC](https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901 "2017-06-04T11:30:22Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![daath](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/daath/32/115536_2.png) [@daath](https://meta.discourse.org/u/daath)\
**Post date:** [2017年六月4日 11:30 UTC](https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901/1 "2017-06-04T11:30:22Z")

</div>

These kind of links worked not very long ago:

[http://tjek.nu/r/8YCX](http://tjek.nu/r/8YCX)

[http://e-liquid-recipes.com/recipe/1121597/Banana%20Cream%20Pie%20(Gmix)](http://e-liquid-recipes.com/recipe/1121597/Banana%20Cream%20Pie%20%28Gmix%29)

Producing oneboxes like this:

 ![](https://global.discourse-cdn.com/meta/original/3X/d/4/d40c36e6471550322dcca35030039ccfbe38c7b8.png)

But not any longer - I tried inputting them on:

> **[Iframely URL Debugger - Open Graph, Twitter Cards, oEmbed](https://debug.iframely.com)**
>
> Check your URL against Open Graph, Twitter Cards, oEmbed specs. See what other apps see.

But I couldn’t see what was wrong… Especially when I compared the output to Discourse’s own output…

Can someone point me in the right direction?

---

<div class="post-metadata">

**Author:** ![daath](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/daath/32/115536_2.png) [@daath](https://meta.discourse.org/u/daath)\
**Post date:** [2017年六月6日 14:51 UTC](https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901/3 "2017-06-06T14:51:12Z")

</div>

No insight on this? I still doesn’t work on my site (which used to work fine)…

---

<div class="post-metadata">

**Author:** ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)\
**Post date:** [2017年六月6日 14:53 UTC](https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901/4 "2017-06-06T14:53:30Z")

</div>

It’s only been 2 days. You have to give us a little while to get to things 🙂

---

<div class="post-metadata">

**Author:** ![daath](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/daath/32/115536_2.png) [@daath](https://meta.discourse.org/u/daath)\
**Post date:** [2017年六月6日 15:13 UTC](https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901/5 "2017-06-06T15:13:47Z")

</div>

haha sorry, you’re right - it did prompt me to investigate further.

It looks like the onebox’er sends a HEAD request, which would explain it not working on my site, as I only support GET and POST. Doing a HEAD results in a 501 Not Implemented. When did this change?

---

<div class="post-metadata">

**Author:** ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)\
**Post date:** [2017年六月6日 15:16 UTC](https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901/6 "2017-06-06T15:16:03Z")

</div>

Ah, this is a recent change to improve security with redirects.

I’ve been meaning to make it so that if the HEAD request receives a 501 it tries a GET. I will add that to my list.

---

<div class="post-metadata">

**Author:** ![daath](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/daath/32/115536_2.png) [@daath](https://meta.discourse.org/u/daath)\
**Post date:** [2017年六月6日 15:23 UTC](https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901/7 "2017-06-06T15:23:21Z")

</div>

Excellent. Now I know why, and that the problem is in very capable hands. Now I just have to ask my users to be patient 🙂 Thanks! 😃

---

<div class="post-metadata">

**Author:** ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)\
**Post date:** [2017年六月6日 19:23 UTC](https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901/8 "2017-06-06T19:23:13Z")

</div>

It’s fixed now:

[http://e-liquid-recipes.com/recipe/1121597/Banana%20Cream%20Pie%20(Gmix)](http://e-liquid-recipes.com/recipe/1121597/Banana%20Cream%20Pie%20%28Gmix%29)

Was quite involved. The fix wasn’t as simple as to try HTTP GET, but it also involved supporting cookies on redirects which our more secure redirector did not do. Both are supported now.

[https://github.com/discourse/discourse/commit/53b95f009fc457f033427147ce34b4aa2e472f74](https://github.com/discourse/discourse/commit/53b95f009fc457f033427147ce34b4aa2e472f74)

[https://github.com/discourse/discourse/commit/369bb78f8e49c4cc4c3b585b40e4dc143a8b2669](https://github.com/discourse/discourse/commit/369bb78f8e49c4cc4c3b585b40e4dc143a8b2669)

[https://github.com/discourse/onebox/commit/ea4a45bbf452bc3c40d470889daf21faa7fa6ba0](https://github.com/discourse/onebox/commit/ea4a45bbf452bc3c40d470889daf21faa7fa6ba0)

---

<div class="post-metadata">

**Author:** ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)\
**Post date:** [2017年六月6日 19:23 UTC](https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901/9 "2017-06-06T19:23:22Z")

</div>


