Markdown cache
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
For performance reasons, GitLab caches the HTML version of Markdown text in fields such as:
- Comments.
- Issue descriptions.
- Merge request descriptions.
These cached versions can become outdated, such as when the external_url
configuration option is changed. Links
in the cached text would still refer to the old URL.
Invalidate the cache
Pre-requisite:
- You must be an administrator.
To avoid problems caused by cached HTML versions, invalidate the existing cache by increasing the local_markdown_version
setting in application settings using the API:
curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings?local_markdown_version=<increased_number>"
Docs
Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.
Product
Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Feature availability and product trials
View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.
Get help
If you didn't find what you were looking for, search the docs.
If you want help with something specific and could use community support, post on the GitLab forum.
For problems setting up or using this feature (depending on your GitLab subscription).
Request support