Home

Awesome

WRP - Web Rendering Proxy

A browser-in-browser "proxy" server that allows to use historical / vintage web browsers on the modern web. It has two modes:

Internet Explorer 1.5 doing Gmail

Usage Instructions

Image Map Mode

Simple HTML mode

UI explanation

The first unnamed input box is either search (google) or URL starting with http/https

Go instructs browser to navigate to the url or perform search

Bk is History Back

St is Stop, also re-capture screenshot without refreshing page, for example if page render takes a long time or it changes periodically

Re is Reload

W is width in pixels, adjust it to get rid of horizontal scroll bar

H is height in pixels, adjust it to get rid of vertical scroll bar. It can also be set to 0 to produce one very tall image and use client scroll. This 0 size is experimental, buggy and should be used with PNG and lots of memory on a client side.

Z is zoom or scale

C is colors, for GIF images only (unused in PNG, JPG)

K is keystroke input, you can type some letters in it and when you click Go it will be typed in the remote browser.

Bs is backspace

Rt is return / enter

< ^ v > are arrow keys, typically for navigating a map, buggy.

UI Customization

WRP supports customizing it's own UI using HTML Template file. Download wrp.html place in the same directory with wrp binary customize it to your liking.

Docker

https://hub.docker.com/r/tenox7/wrp

$ docker run -d --rm -p 8080:8080 tenox7/wrp:latest

AWS

It's possible to run WRP on AWS App Runner.

First you need to upload the Docker image to ECR - Instructions.

Create App Runner service using the uploaded image using the AWS Console or CLI.

AWS Console

aws apprunner create-service --service-name my-app-runner-service --source-configuration '{
    "ImageRepository": {
        "ImageIdentifier": "<account_id>.dkr.ecr.<region>.amazonaws.com/wrp:latest",
        "ImageRepositoryType": "ECR",
        "ImageConfiguration": {"Port": "8000"},
        "AutoDeploymentsEnabled": true
    }
}' --instance-configuration '{
    "Cpu": "1024",
    "Memory": "2048",
    "InstanceRoleArn": "arn:aws:iam::<account_id>:role/AppRunnerECRAccessRole"
}'

Azure Container Instances

Azure Console

CLI:

$ az container create --resource-group wrp --name wrp --image tenox7/wrp:latest --cpu 1 --memory 2 --ports 80 --protocol tcp --os-type Linux --ip-address Public --command-line '/wrp -l :80 -t png -g 1280x0x256'

Google Cloud Run

$ gcloud run deploy --platform managed --image=tenox7/wrp:latest --memory=2Gi --args='-t=png','-g=1280x0x256'

Unfortunately Google Cloud Run forces you to use HTTPS, which likely won't work with old browsers.

Flags

-l   listen address:port (default :8080)
-m   mode, either ismap (graphical) or html
-t   image type gif, png or jpg (default gif)
-g   image geometry, WxHxC, height can be 0 for unlimited (default 1152x600x216)
     C (number of colors) is only used for GIF
-q   Jpeg image quality, default 75%
-h   headless mode, hide browser window on the server (default true)
-d   chromedp debug logging (default false)
-n   do not free maps and images after use (default false)
-ui  html template file (default "wrp.html")
-ua  user agent, override the default "headless" agent (only for ismap mode)
-s   delay/sleep after page is rendered before screenshot is taken (default 2s)

Minimal Requirements

FAQ

I can't get it to run

This program does not have a GUI and is run from the command line. After downloading, you may need to enable executable bit on Unix systems, for example:

$ cd ~/Downloads
$ chmod +x wrp-amd64-macos
$ ./wrp-amd64-macos

Websites are blocking headless browsers

This is a well known issue. WRP has some provisions to work around it, but it's a cat and mouse game. The first and foremost recommendation is to change the User Agent, so that it doesn't say "headless". Add -ua="my agent" to override the default one. Obtain your regular desktop browser user agent and specify it as the flag. For example:

$ wrp -ua="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"

Why is WRP called "proxy" when it's not

WRP originally started as true http proxy. However this stopped working because the whole internet is now encrypted thanks to Let's Encrypt. Legacy browsers do not support modern SSL/TLS certs as well as HTTP CONNECT so this mode had to be disabled.

Will you support http proxy mode in future?

Some efforts (ssl strip) are under way but it's very difficult to do it correctly and the priority is rather low.

Why isn't there a Docker image for armv6

Because https://hub.docker.com/r/chromedp/headless-shell/ doesn't have one. WRP uses that image. If you have a fork that builds for armv6 let me know.

History

Credits

Related

You may also be interested in:

Legal Stuff

License: Apache 2.0
Copyright (c) 2013-2024 Antoni Sawicki
Copyright (c) 2019-2024 Google LLC