retro-proxy VS MicroWeb

https://theoldnet.com/ https://github.com/tenox7/wrp https://github.com/DrKylstein/retro-proxy

Retro-proxy is the biggest contributor. It handles https to http, strips out javascript and css, resizes images a bit, and minifies html. It helps a lot.

Net traffic is being proxied through retro-proxy to handle SSL and minifying some of the content. Details of the in-house 'ISP' I'm using can be found here.

I have Linux computers and a Windows 10 mothership and have looked at https://github.com/DrKylstein/retro-proxy but there's very little documentation and I can't even tell if Retro Proxy provides a proxy address, let alone makes it available to the DOS machine.

Also thanks to DrKylestein for [Retro Proxy](https://github.com/DrKylstein/retro-proxy)

Also thanks to DrKylestein for Retro Proxy

On the server mgetty is configured for normal tty access, but also to support /AutoPPP/, which kicks off a pppd session and allows machines to connect via PPP like any dial-up internet provider. net.ipv4.forward is set to 1, and ipfwadm is set up to forward traffic. The server acts as a router, doing NAT for the dial-up client. Works great, though I do have browservice and retro-proxy servers running on a VM to handle https -> http and/or rendering for websites too modern for older browsers.

MicroWeb[0] similarly provides a DOS web browser that works on CGA today.

0. https://github.com/jhhoward/MicroWeb

Microweb, a browser designed to be run on 8088 machines

MicroWeb DOS web browser – for 8088 systems\ (7 comments)

Thanks to jhhoward for their work on [Microweb](https://github.com/jhhoward/MicroWeb)

Thanks to jhhoward for their work on Microweb

In another video I have the laptop connect directly to Reddit using a browser called Microweb instead, though in that case it's actually connecting to a proxy running on the server that handles translation of https to http.