-
```
The Expect: 100-continue mechanism is explained in RFC 2616 sections 8.2.3
(http://www.rfc.net/rfc2616.html#s8.2.3) and the WSGI requirements for it
are described in PEP 333
(http://www.python.org…
-
```
The Expect: 100-continue mechanism is explained in RFC 2616 sections 8.2.3
(http://www.rfc.net/rfc2616.html#s8.2.3) and the WSGI requirements for it
are described in PEP 333
(http://www.python.org…
-
```
The Expect: 100-continue mechanism is explained in RFC 2616 sections 8.2.3
(http://www.rfc.net/rfc2616.html#s8.2.3) and the WSGI requirements for it
are described in PEP 333
(http://www.python.org…
-
```
The Expect: 100-continue mechanism is explained in RFC 2616 sections 8.2.3
(http://www.rfc.net/rfc2616.html#s8.2.3) and the WSGI requirements for it
are described in PEP 333
(http://www.python.org…
-
```
The Expect: 100-continue mechanism is explained in RFC 2616 sections 8.2.3
(http://www.rfc.net/rfc2616.html#s8.2.3) and the WSGI requirements for it
are described in PEP 333
(http://www.python.org…
-
```
The Expect: 100-continue mechanism is explained in RFC 2616 sections 8.2.3
(http://www.rfc.net/rfc2616.html#s8.2.3) and the WSGI requirements for it
are described in PEP 333
(http://www.python.org…
-
**Describe the bug**
See the code example: basically certain cases using `raise_on_no_answer=False` produce astonishing behavior when trying to evaluate the result of the dns.resolver.resolve() metho…
-
```
The Expect: 100-continue mechanism is explained in RFC 2616 sections 8.2.3
(http://www.rfc.net/rfc2616.html#s8.2.3) and the WSGI requirements for it
are described in PEP 333
(http://www.python.org…
-
```
The Expect: 100-continue mechanism is explained in RFC 2616 sections 8.2.3
(http://www.rfc.net/rfc2616.html#s8.2.3) and the WSGI requirements for it
are described in PEP 333
(http://www.python.org…
-
```
The Expect: 100-continue mechanism is explained in RFC 2616 sections 8.2.3
(http://www.rfc.net/rfc2616.html#s8.2.3) and the WSGI requirements for it
are described in PEP 333
(http://www.python.org…