Fixed Encodings other than UTF-8 isn't properly supported in unfurling URLs

Vlady

Member
Affected version
2.1 beta 4
Last edited:
Thank you for reporting this issue. The issue is now resolved and we are aiming to include that in a future XF release (2.1.0 Beta 5).

Change log:
Ensure the Content-Type header is pulled from the metadata correctly, ensure the correct charset is pulled only from actual meta tags, and attempt charset conversion sooner and reflect the charset conversion within the HTML source before crawling it.
Any changes made as a result of this issue being resolved may not be rolled out here until later.
 
Back
Top Bottom