and then when this error is received, the response contains a non-JSON body. Triggering another error - "Unexpected token < in JSON at position 0"