Thanks for reporting - same bug as this one - HTTP error content is empty (unexpected per documentation)