Projects / rproxy

git clone https://molodetz.nl/retoor/rproxy.git copy

Files

rproxy

Author: retoor retoor@molodetz.nl

A high-performance reverse proxy server written in C. Routes HTTP and WebSocket requests to upstream services based on hostname, with support for SSL/TLS connections and real-time monitoring.

Features

• Reverse proxy routing by hostname
• SSL/TLS support for upstream connections with certificate verification
• WebSocket proxying
• Connection pooling and idle timeout management
• Real-time monitoring and statistics
• Web-based dashboard for metrics visualization
• SQLite-based persistent statistics storage
• Epoll-based event handling for high concurrency
• Graceful shutdown with connection draining
• Live configuration reload via SIGHUP
• Per-route authentication (HTTP Basic Auth)
• Dashboard authentication
• Rate limiting per client IP
• Health checks for upstream servers
• Automatic upstream connection retries
• File logging support
• Stream data patching/rewriting for textual content

Dependencies

• GCC
• OpenSSL (libssl, libcrypto)
• SQLite3
• pthreads
• cJSON (bundled)

Build

make

Compiles the source files in src/ and produces the rproxy executable.

Testing

make test           # Run unit tests
make coverage       # Run tests with coverage report (minimum 69% required)
make coverage-html  # Generate HTML coverage report
make valgrind       # Run tests with memory leak detection

Test Results

Test Results: 741/741 passed

HEAP SUMMARY:
    in use at exit: 0 bytes in 0 blocks
  total heap usage: 155,794 allocs, 155,794 frees, 13,900,573 bytes allocated

All heap blocks were freed -- no leaks are possible

ERROR SUMMARY: 0 errors from 0 contexts

Configuration

Configuration is defined in proxy_config.json :

{
  "port": 9998,
  "reverse_proxy": [
    {
      "hostname": "example.com",
      "upstream_host": "127.0.0.1",
      "upstream_port": 5000,
      "use_ssl": false,
      "rewrite_host": true,
      "use_auth": true,
      "username": "admin",
      "password": "secret",
      "patch": {
        "old_string": "new_string",
        "blocked_content": null
      }
    }
  ]
}

Route Options

Data Patching

The patch configuration allows rewriting or blocking content in HTTP streams. Patch rules are applied to textual content only. Binary content passes through unmodified.

{
  "patch": {
    "find_this": "replace_with_this",
    "another_string": "replacement",
    "blocked_term": null
  }
}

• String replacement : Each key-value pair defines a find-replace rule
• Content blocking : Setting value to null blocks the entire response/request when the key is found
• Bidirectional : Patches apply to both requests and responses

Blocked responses return 502 Bad Gateway . Blocked requests return 403 Forbidden .

Supported textual content types:

• text/*
• application/json
• application/xml
• application/javascript
• application/x-www-form-urlencoded
• Content types with +xml or +json suffix

Environment Variables

Usage

./rproxy [config_file]

If no config file is specified, defaults to proxy_config.json .

./rproxy
./rproxy /etc/rproxy/config.json
DEBUG=1 ./rproxy
LOG_FILE=/var/log/rproxy.log ./rproxy
RATE_LIMIT=100 ./rproxy
DASHBOARD_USER=admin DASHBOARD_PASS=secret ./rproxy
SSL_VERIFY=0 ./rproxy
kill -HUP $(pidof rproxy)  # Reload configuration

Endpoints

Signals

Architecture

License

See LICENSE file for details.

Files