Since moving our Medium blog to our own subdomain, we are consistently having this error every time we share a blog post on our forum. I have validated the links with OpenGraph, and they seem to work fine. Examples: https://blog.sphere.me/one-year-into-lockdown-how-has-work-life-balance-changed-ad48aa73e57f?source=collection_home---4------1----------------------- https://blog.sphere.me/chrissy-teigen-and-twitters-reckoning-where-do-digital-spaces-go-from-here-40bf4c149752 [Screenshot 2021-03-25 at 17.40.40] screenshot from opengraph.xyz (p.s talljeff says hi to jeff a!)

[이미지] simonb: https://blog.sphere.me/chrissy-teigen-and-twitters-reckoning-where-do-digital-spaces-go-from-here-40bf4c149752 Something about your setup is weird. If I issue a GET to this URL I get a sequence of redirects: GET → 307 → 302 → 200 However, if I issue a HEAD I get a 200 straight away HEAD → 200 The way our onebox works is that we try to handle all the redirection dance with a HEAD request first, and pass the already resolved URL and the necessary cookies to the oneboxer engine. Since your setup is doing different responses for each, this breaks onebox. It’s also quite bad for perfomance when the canonical URL for the article is always two redirects away from rendering, so you may want to fix that.

Thanks Rafael, All we did (as far as I’m aware) was use Medium’s new custom domain implementation and created the relevant A Name records. Would this therefore be an issue to raise with Medium? I’ve asked our Head of Infrastructure in case it’s something with how our domain is set up.

Maybe contact Medium support about it?

hi @Falco - i have heard back from Medium support, and this is what they have asked. Could you tell us what User-Agent header Onebox is sending? We can skip that redirects for requests from bots/scrapers that we can identify. Could you please let me know how best to respond :pray:

[이미지] simonb: (p.s talljeff says hi to jeff a!) Whoa! I missed this! Send him a hug :hugs: We can also repro with this medium entry which also generates a 500. https://crypto-anonymous-2021.medium.com/the-bit-short-inside-cryptos-doomsday-machine-f8dcf78a64d3

@eviltrout hope it’s OK to tag you as I see you worked on this before. Is this still the correct user agent header that I can send to Medium support? [이미지] Onebox user agent Feature This commit adds a custom User-Agent to discourse oneboxes: https://github.com/discourse/discourse/commit/8bc93c0b018045bf23769b8ecc4ec5b493368667 The User agent looks like this: Discourse Forum Onebox v1.8.0.beta13

@simonb the failure to onebox was tracked to a bug handling the 307 response here: [이미지] Falco: GET → 307 → 302 → 200 This PR will fix it when merged: https://github.com/discourse/onebox/pull/476/files

That’s fantastic news. Thank you so much! :purple_heart:

https://blog.sphere.me/one-year-into-lockdown-how-has-work-life-balance-changed-ad48aa73e57f?source=collection_home---4------1----------------------- The Onebox fixes have been merged in and deployed. You should be good to go now!

Amazing! Thank you so much. Looks like I’ve got a few posts to go back and edit tomorrow :smiling_face:

새 블로그가 원박싱되지 않아요

제품 지원

Falco (Falco) 5월 11, 2021, 4:41오후 10

@simonb onebox 처리 실패는 여기의 307 응답 처리 버그로 확인되었습니다:

이 PR이 병합되면 수정됩니다:

Onebox previews are not working for my site

글		댓글	조회수
Medium oneboxes are broken Product Support	6	1468	12월 27, 2017
Medium Onebox support Feature	7	1117	1월 6, 2024
Onebox no longer works for my wordpress site Product Support	11	1928	6월 12, 2017
Bug in onebox - link being rendered as a Gist when it isn't Product Support	3	656	9월 9, 2021
Did onebox change? They're not showing for my main site any longer Product Support	6	1497	6월 6, 2017

새 블로그가 원박싱되지 않아요

Related topics