# Prevent to linkify when there is a redirect

**URL:** <https://meta.discourse.org/t/prevent-to-linkify-when-there-is-a-redirect/226964>\
**Category:** Feature\
**Created:** [May 13, 2022, 4:06pm UTC](https://meta.discourse.org/t/prevent-to-linkify-when-there-is-a-redirect/226964 "2022-05-13T16:06:43Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [May 17, 2022, 12:20am UTC](https://meta.discourse.org/t/prevent-to-linkify-when-there-is-a-redirect/226964/4 "2022-05-17T00:20:08Z")

</div>

> [@Jonathan\_Poyer](#):
>
> This seems to not work for the linkified link that are not updated into “onebox” but just being turned into a title (e.g our internal link [Log in - Sqills Jira](https://support.sqills.com/browse/SCQI-934) turns into `Log in - Sqills Jira` but the base URL just gives `https://support.sqills.com` as title of the link).

There is certainly a confusing bug here we should get sorted.

I just blocked `support.sqills.com` and confirm it is doing what it is supposed to for [https://support.sqills.com/browse/SCQI-934?1](https://support.sqills.com/browse/SCQI-934?1) [https://support.sqills.com/browse/SCQI-934?1](https://support.sqills.com/browse/SCQI-934?1) but sadly `https://support.sqills.com/browse/SCQI-934` is cached server side for 24 hours and rebuilding HTML is not busting the cache.

We will get this small niggle sorted out this week so we reduce support around this. Blocking redirect as an option sounds great to me, we may be able to squeeze this in. Maybe `block onebox on cross domain redirect` is better, or maybe that is too much fidelity… not sure.

---

_[View the full topic](https://meta.discourse.org/t/prevent-to-linkify-when-there-is-a-redirect/226964)._