When you post a link from Stack Exchange into the chatbox using HTTPS, the link does not onebox. However, if you change the link to HTTP, it works. See the screenshot below:

enter image description here

HTTPS URLs should onebox, too.

  • 1
    Eh, the original is two years old - and was written before we started rolling https out network wide. Kinda inclined to leave this one, when links turn into HTTPS, oneboxing is going to need love. – Tim Post Jan 9 '14 at 15:33
  • 2
    @Tim so maybe make that older request dupe of this one? Essentially these are both the same thing after all. – Shadow The Princess Wizard Jan 9 '14 at 15:45
  • 3
    "This question has been asked before and already has an answer." -> the old one doesn't have an answer.. I don't know how to handle these stuff (old dupes). I don't care if this one gets closed.. but I just want to get the attention of the devs regarding this.. – reikyoushin Jan 9 '14 at 17:34
  • 2
    Reopened and flipped the close, where I also notice that using https links in the field where you put the question breaks as well. – Tim Post Jan 10 '14 at 5:24
  • 2
    @TimPost You think you could reach out to any of the SO people by any chance? There is also the issue of other https links not one boxing in general. And the fact that on main there is also still non https content on the page (e.g. imgur). Or can I create a new question with all the https stuff which is likely to get closed as a dupe of some other question(s). – PeeHaa Jan 12 '14 at 1:05
  • 1
    @PeeHaa They're aware of it, I'll see what I can find out early next week. – Tim Post Jan 12 '14 at 9:22
  • @Oded this is not status-completed. HTTPS links (I've observed xkcd) still do not onebox. – Madara Uchiha Jun 16 '15 at 18:07
  • @MadaraUchiha - they mostly do. I think this may happen with timeouts to the source server (more common with HTTPS). A page refresh will normally show things oneboxed. – Oded Jun 18 '15 at 9:21

You must log in to answer this question.

Browse other questions tagged .