##// END OF EJS Templates
hgweb: all protocol functions have become generators...
hgweb: all protocol functions have become generators Using the write() callable supplied by the start_response() call is frowned upon by the WSGI spec, returning an iterable over the content chunks is the recommended way. Be aware, though: returning many small chunks will slow down responses, because the server has to flush each chunk separately.

File last commit:

r5561:22713dce default
r6784:18c429ea default
Show More
get-with-headers.py
20 lines | 590 B | text/x-python | PythonLexer
/ tests / get-with-headers.py
Eric Hopper
Add a test for getting raw files via the web UI.
r2532 #!/usr/bin/env python
__doc__ = """This does HTTP get requests given a host:port and path and returns
a subset of the headers plus the body of the result."""
import httplib, sys
headers = [h.lower() for h in sys.argv[3:]]
conn = httplib.HTTPConnection(sys.argv[1])
conn.request("GET", sys.argv[2])
response = conn.getresponse()
print response.status, response.reason
for h in headers:
if response.getheader(h, None) is not None:
print "%s: %s" % (h, response.getheader(h))
print
sys.stdout.write(response.read())
Bryan O'Sullivan
hgweb: return meaningful HTTP status codes instead of nonsense
r5561
if 200 <= response.status <= 299:
sys.exit(0)
sys.exit(1)