Skip to main content

A super simple reverse proxy.

Project description

A super simple HTTP/1.1 proxy, with TLS support.

Install from PyPI:

$ pip install rproxy

Make a rproxy.ini:

[rproxy]
certs=certificates
http_ports=80
https_ports=443

[hosts]
mysite.com_port=8080

Then run it:

sudo twistd -u nobody -g nobody -n rproxy

This will start the server, drop permissions (setting the effective uid/guid to nobody), and will proxy incoming requests to mysite.com to localhost:8080. You can configure it further:

[rproxy]
certs=certificates
letsencrypt=le
http_ports=80,8080
https_ports=443
clacks=true

[hosts]
mysite.com_port=8080
mysite.com_host=otherserver
mysite.com_onlysecure=True
mysite.com_proxysecure=True

myothersite.net_port=8081

This config will:

  • connect to https://otherserver:8080 as the proxied server for mysite.com, and only allow HTTPS connections to the proxy for this site

  • connect to http://localhost:8081 as the proxied server for myothersite.net, and allow HTTP or HTTPS connections.

General Config

  • http_ports – comma-separated list of numerical ports to listen on for HTTP connections.

  • https_ports – comma-separated list of numerical ports to listen on for HTTPS connections.

  • certificates – directory where certificates are kept. rproxy looks for <host>.pem in this folder when serving HTTPS sites.

  • letsencrypt – directory where Let’s Encrypt ACME challenges are kept – the “webroot” parameter for https://github.com/kuba/simp_le . rproxy looks for <host>/.well-known/acme-challenge in this folder when serving Let’s Encrypt HTTP-01 challenges.

  • clacks – Enable X-Clacks-Overhead for requests.

Hosts Config

  • <host>_onlysecure – enforce HTTPS connections. If not set, or set to False, it will allow HTTP and HTTPS connections.

  • <host>_proxysecure – connect to the proxied server by HTTPS. If not set, or set to False, it will connect over HTTP.

  • <host>_port – The port of the proxied server that this proxy should connect to.

  • <host>_host – the hostname/IP of the server to proxy to.

  • <host>_sendhsts – send HSTS headers on HTTPS connections.

  • <host>_wwwtoo – match www too. (Note: if you are using TLS, you will need a www.<host>.pem in your certificates directory too!)

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

rproxy-16.3.1.tar.gz (4.3 kB view details)

Uploaded Source

File details

Details for the file rproxy-16.3.1.tar.gz.

File metadata

  • Download URL: rproxy-16.3.1.tar.gz
  • Upload date:
  • Size: 4.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No

File hashes

Hashes for rproxy-16.3.1.tar.gz
Algorithm Hash digest
SHA256 064cce0599f7556c85d079f3c4448bcba06485b21d1b4ed4e2328f25b1e7e575
MD5 bc640b233464435c86004a602966b72a
BLAKE2b-256 607bdc59c8242f709f9f378aaaaca8837072ac4647c1dee1d5d693d810b2dab8

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page