# Onebox requests being incorrectly redirected due to user-agent **URL:** https://meta.discourse.org/t/onebox-requests-being-incorrectly-redirected-due-to-user-agent/120557 **Category:** Support **Created:** [6월 17, 2019, 7:07오전 UTC](https://meta.discourse.org/t/onebox-requests-being-incorrectly-redirected-due-to-user-agent/120557 "2019-06-17T07:07:06Z") **Posts on this page:** 1 **Showing post:** 3
### Author: ![JezPez](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jezpez/32/145071_2.png) [@JezPez](https://meta.discourse.org/u/JezPez) #### Post date: [6월 17, 2019, 7:50오전 UTC](https://meta.discourse.org/t/onebox-requests-being-incorrectly-redirected-due-to-user-agent/120557/3 "2019-06-17T07:50:05Z")
A curl request responds with html which seems like it’s actually rendering the whole card. `curl -X GET https://link.jig.space/gXszoFiWkX` ```plaintext Macintosh - Complete
JigSpace
Macintosh - Complete
Apple Macintosh Computer
``` If OneBox’s issue is the image issue which FB is complaining about, then we should add the FB open graph debugger to the OneBox docs thread: [Creating rich link previews with Onebox](https://meta.discourse.org/t/rich-link-previews-with-onebox/98088) I’ll try to put in the og:image:width and such as FB suggests. Thanks @merefield. --- _[View the full topic](https://meta.discourse.org/t/onebox-requests-being-incorrectly-redirected-due-to-user-agent/120557)._