4 Commits (bdmurray/intel-iot-models)

Author	SHA1	Message	Date
Dimitri John Ledkov	dc2a472871	magic-proxy: replace http.client with urllib calls ... Initialize passwords from sources.list. Use urllib everywhere. This way authentication is added to all the required requests. And incoming headers, are passed to the outgoing requests. And all the response headers, are passed to the original client. And all the TCP & HTTP errors are passed back to the client. Thus should avoiding hanging requests upon failure. Also rewrite the URI when requesting things. This allows to use private-ppa.buildd outside of launchpad. Signed-off-by: Dimitri John Ledkov <xnox@ubuntu.com>	4 years ago
Robert C Jennings	c10ca357b5	magic-proxy: Send headers on error (LP: #1829944)	6 years ago
Tobias Koch	3a294f5b50	magic-proxy: return 404 when InRelease file cannot be found "by hash" ... When the magic-proxy script could not find a valid InRelease file for the configured timestamp, it would fall back to serving the canonical version of it. This meant that builds would succeed, even though snap-shotting the repository failed. This update makes the script return HTTP 404 when an InRelease by-hash link for a given combination of mirror, suite and timestamp cannot be found.	6 years ago
Tobias Koch	5b70d86f5c	Inject a proxy into the build providing a snapshot view of the package repo. ... When the REPO_SNAPSHOT_STAMP variable is set, the auto/build script will attempt to launch a transparent HTTP proxy on port 8080, and insert an iptables rule to redirect all outgoing HTTP requests to this proxy. The proxy, contained in the `magic-proxy` Python script, examines each request and silently overrides those pointing to InRelease files or files that are listed in InRelease files. It will instead provide the contents of the requested file as it was at REPO_SNAPSHOT_STAMP, by downloading the corresponding asset "by hash".	6 years ago