Custom protocol links not working in issue description

Summary

Steps to reproduce

Writing [Link](unibox://message/) in an issue gets rendered correctly in the preview, but without the href attribute when submitting the message:

Link

This also happens when entering unibox://message/ directly:

unibox://message/

And also when entering <a href="unibox://message/">Link</a> directly:

Link

Example Project

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

changed title from Custom protocol links not working in markdown links to Custom protocol links not working in issue description

changed the description

mentioned in issue gitlab-org/quality/triage-reports#1227 (closed)

added automation:ml groupproject management labels

Setting label(s) devopsplan sectiondev based on groupproject management.

added devopsplan sectiondev labels

added typebug label

mentioned in issue gitlab-org/quality/triage-reports#1372 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1437 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1515 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1601 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1690 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1793 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1886 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1987 (closed)

I would really like to see this working. I even think that this worked in an earlier version without problem. However, there are many more protocols used during development than the standard ones. In my opinion / in my line of work this borders on a show-stopper.

I can understand that some people regard this as security issue. However, the user should be able to configure the project according to his needs.

added vintage label

Hi @mondly-iulian-onofrei ,

Thanks for raising this bug.

Contributions like this are vital to help make GitLab a better product.

We would be grateful for your help in verifying whether your bug report requires further attention from the team. If you think this bug still exists, and is reproducible with the latest stable version of GitLab, please comment on this issue.

This issue has been inactive for more than 12 months now and based on the policy for inactive bugs, will be closed in 7 days.

Thanks for your contributions to make GitLab better!

Link

It now doesn't work in the preview either.

added stale label

removed stale label

Please mark this as duplicate of #275975 (closed), and close it, as it works correctly now.

closing

closed

marked this issue as a duplicate of #275975 (closed)

marked this issue as related to #275975 (closed)