httpx.exceptions.RemoteProtocolError: malformed data

Originally opened by @shimachao on 2020-10-15 12:12:16 in encode/httpx

Checklist

• The bug is reproducible against the latest release and/or master.
• There are no similar issues or pull requests to fix it yet.

Describe the bug

When server returns bad headers,RemoteProtocolError occurred

To reproduce

headers = {
"Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,"
"image/avif,image/webp,image/apng,/;q=0.8,application/"
"signed-exchange;v=b3;q=0.9",
"Accept-Encoding": "gzip, deflate, br",
"Accept-Language": "zh-CN,zh;q=0.9",
"User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) "
"AppleWebKit/537.36 (KHTML, like Gecko) Chrome/"
"86.0.4240.75 Safari/537.36"}
client= httpx.AsyncClient(headers=headers, timeout=120,verify=False, proxies=proxies)
await client.get("https://club.huawei.com/forum.html")

Expected behavior

Actual behavior

Debugging material

Environment

• OS:
• Python version: 3.8.5
• HTTPX version: 0.16.1
• Async environment: asyncio
• HTTP proxy: no
• Custom certificates: no

Additional context

bad header:
get-ban-to-cache-result/forum.php: userdata not support

No source file or test is named. Start by reproducing the asyncio request to https://club.huawei.com/forum.html with the supplied headers and environment, then inspect the full traceback and HTTP response parsing path. The issue does not state the expected handling of the malformed header or define a completion test.