Noah Kantrowitz <n...@coderanger.net> writes: >> >> >> the xmlrpc api is broken when using http 1.0. the second call to curl >> uses http/1.0 and returns an empty response: >> >> $ cat >body.txt <<EOF >> <?xml version='1.0'?> >> <methodCall> >> <methodName>package_releases</methodName> >> <params> >> <param> >> <value><string>e</string></value> >> </param> >> </params> >> </methodCall> >> EOF >> $ curl -X POST -d @body.txt http://pypi.python.org/pypi --header >> "Content-Type:text/xml" >> <?xml version='1.0'?> >> <methodResponse> >> <params> >> <param> >> <value><array><data> >> <value><string>1.4.5</string></value> >> </data></array></value> >> </param> >> </params> >> </methodResponse> >> $ curl -0 -X POST -d @body.txt http://pypi.python.org/pypi --header >> "Content-Type:text/xml" >> $ > > We have not supported HTTP 1.0 for quite some time.
well, it has been working until at least last friday. > Even before the CDN move, we used the Host header to route between > different HAProxy server blocks on the load balancers. I'm unaware of > any reason people would be using HTTP 1.0 clients at this point, HTTP > 1.1 has been a standard for 14 years now. the fact that you are unaware of any reason people would be using HTTP 1.0 is not a good reason not to support it. python 2.6 xmlrpclib uses HTTP/1.0! -- Cheers Ralf _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
