![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
An xml file keep misidentified as an html file without any visible reason
Recently, after my computer get repaired, I had to do various things, such as reinstall some software and, in the case of Firefox, put back my bookmarks and rss feeds (they were lost and if there was a backup, I didn't find it)
The problem only happen with this page. I didn't find any other page with this problem.
I checked all what I can about this page (using view-source). I compared it with other xml files, mostly other rss, and the documentation I found about rss, xml and html. Visibly, this is a regular xml/rss page. I didn't found anything special in.
There are element underlined in red in the source code but it is mostly what can be seen as an error if this is parsed at assuming it's html code.
I also check what I get if I do a right click then, in the contextual menu, I select "inspecter" (sorry, on my computer, Firefox is set to french and I don't know the english term ; this is the last entry of the menu). I got a different code. Apparently, Firefox applied (pseudo) fixes to display the page as an html document.
I checked the name of the page. This is unusual but, in my rss feeds, there are several other rss feeds named this kind of way and all of them work properly.
The last thing I checked is the RSS link that is on most pages of the site and send to this glitched page. It doesn't seem to be more the cause.
Visibly, for an unknown reason, Firefox decreed this is html code and I found no way to make it reconsider this or parse this page as xml.
It seem the first mention of problem with the rss feed on this site was a comment written almost four months ago but I don't know if it was the same problem.
글쓴이 asmanel 수정일시
모든 댓글 (1)
The server is sending this header:
Content-Type: text/html; charset=UTF-8
So that is why Firefox treats it as HTML. I can't think of a quick way to fix this. (I have an add-on that can fix mistaken content types based on the file extension, but this page doesn't have a .xml file extension.)