# Onebox does not work when summary opengraph tag is not present?

**URL:** <https://meta.discourse.org/t/onebox-does-not-work-when-summary-opengraph-tag-is-not-present/61953>\
**Category:** Product Support\
**Created:** [02.Май.2017 11:37:54 UTC](https://meta.discourse.org/t/onebox-does-not-work-when-summary-opengraph-tag-is-not-present/61953 "2017-05-02T11:37:54Z")\
**Posts on this page:** 1\
**Showing post:** 30

<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:** [15.Июнь.2017 19:12:12 UTC](https://meta.discourse.org/t/onebox-does-not-work-when-summary-opengraph-tag-is-not-present/61953/30 "2017-06-15T19:12:12Z")

</div>

This is a strange error. The Medium site is returning status [code 409](https://httpstatuses.com/409) when you make a HEAD request which indicates a conflict.

I added 409 to our list of “try again with GET” codes and it’s now working. I’m not sure why they’d consider a HEAD call a conflict but this does seem to fix it:

[https://github.com/discourse/discourse/commit/7366f334b04aa65065f835ecad137853fa94387f](https://github.com/discourse/discourse/commit/7366f334b04aa65065f835ecad137853fa94387f)

---

_[View the full topic](https://meta.discourse.org/t/onebox-does-not-work-when-summary-opengraph-tag-is-not-present/61953)._
