Proxying to another web service with Flask

Question

I want to proxy requests made to my Flask app to another web service running locally on the machine. I'd rather use Flask for this than our higher-level nginx instance so that we can reuse our existing authentication system built into our app. The more we can keep this "single sign on" the better.

Is there an existing module or other code to do this? Trying to bridge the Flask app through to something like httplib or urllib is proving to be a pain.

Answer 1

I spent a good deal of time working on this same thing and eventually found a solution using the requests library that seems to work well. It even handles setting multiple cookies in one response, which took a bit of investigation to figure out. Here's the flask view function:

from flask import request, Response import requests  def _proxy(*args, **kwargs):     resp = requests.request(         method=request.method,         url=request.url.replace(request.host_url, 'new-domain.com'),         headers={key: value for (key, value) in request.headers if key != 'Host'},         data=request.get_data(),         cookies=request.cookies,         allow_redirects=False)      excluded_headers = ['content-encoding', 'content-length', 'transfer-encoding', 'connection']     headers = [(name, value) for (name, value) in resp.raw.headers.items()                if name.lower() not in excluded_headers]      response = Response(resp.content, resp.status_code, headers)     return response 

Update April 2021: excluded_headers should probably include all "hop-by-hop headers" defined by RFC 2616 section 13.5.1.

Answer 2

I have an implementation of a proxy using httplib in a Werkzeug-based app (as in your case, I needed to use the webapp's authentication and authorization).

Although the Flask docs don't state how to access the HTTP headers, you can use request.headers (see Werkzeug documentation). If you don't need to modify the response, and the headers used by the proxied app are predictable, proxying is staightforward.

Note that if you don't need to modify the response, you should use the werkzeug.wsgi.wrap_file to wrap httplib's response stream. That allows passing of the open OS-level file descriptor to the HTTP server for optimal performance.