The point is they either need to filter the served content, or serve it from a different domain (e.g. githubusercontent.com), otherwise you have XSS-like problems.
Re:CSS in GitHub Readmes
by michaelmior on Tuesday December 08, 2020 @02:29PM
(#25350152)
My understanding is that things like this are one of the reasons GitHub moved GitHub Pages subdomains from github.com to github.io.
Re:CSS in GitHub Readmes
by felixfbecker on Tuesday December 08, 2020 @03:22PM
(#25350820)
GitHub raw endpoints do it. They will either serve the SVG without an image/svg+xml Content-Type, making it not render in the browser, or you have to append ?sanitize=true to the URL which will, as the name suggest, sanitize it.
ok but that is github...parent poster stated its common to do that...it is not.
It's web security 101 for handling user uploads. (although in the case of SVG most sites solve it by just not accepting "weird" formats like SVG)
That's definitely not a thing that happens. Web servers just serve the file as-is.