Fixed Invalid Content-Type header for connected_accounts.php errors


Well-known member
Affected version
Ran into an issue where if you get an error with the connected_accounts.php page, you would get an error in the browser saying the site can't be reached with ERR_INVALID_RESPONSE being the reason.

Turns it it was happening when you have Cloudflare (or anything really) setup to add the X-Content-Type-Options: nosniff header because "unknown/unknown" is not a valid content type for browsers.


Might not be a bad idea to assign a valid content type before the send() methods in connected_accounts.php


Lukas W.

Well-known member
I remember one of my members being prompted to download the error by their browser because it failed to interpret the response correctly. Made them think it was a virus. 😒

XF Bug Bot

XenForo bug fixer bot
Staff member
Thank you for reporting this issue. It has now been resolved and we are aiming to include it in a future XF release (2.1.3).

Change log:
Set appropriate content type for connected_account.php output.
Any changes made as a result of this issue being resolved may not be rolled out here until later.