Closed ivan closed 5 years ago
Sounds like Twitter sometimes doesn't send a Content-Type
header. So I guess the solution is to treat any such response as invalid.
I do wonder though what Twitter does send in those cases. It might be a good idea to dump the raw data into the log or to a temporary file in case of an uncaught exception.
This happens (infrequently) when scraping a twitter-user; it looks spurious and not related to a specific user: