That's true as well. So from that aspect if someone's code is not doing the proper checks around it, then it's already _potentially_ broken. I would assume, however, that malformed XML (which would trigger the die) is probably more common than bad HTTP request. 

With that in mind then, I wouldn't be opposed to merging this in once the other issue is resolved (pointed out in comments above), but those other 6 areas pointed out that don't do the proper checks should be fixed in a separate PR.