A string `xx://a:[b]` in a markdown document will result in a 500 response
Summary
A string xx://a:[b] in a markdown document will result
in a 500 response code.
Steps to reproduce
Create a file (README.md) containing the string xx://a:[b]; preview
the file on a 11.7.4 server.
Example Project
https://gitlab.com/xtofl/articles/blob/test_gitlab_markdown_rendering/README.md
Note: this does render allright on gitlab.com!
What is the current bug behavior?
We get a red banner showing "Error loading viewer". The file is not rendered (a wait-for-me spinner is visible). The network response contains a 500 for the url https://gitlabinternal.softathome.com/kristoffel.pirard_ext/articles/tree/test_gitlab_markdown_rendering
What is the expected correct behavior?
The file should be rendered; if not, an error should be shown indicating where the problematic markdown is situated.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Maybe I can come up with this later - I'm not administering our server.
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
(If you can, link to the line of code that might be responsible for the problem)