FudeBrowZer was the graphical web browser for UZIX. It featured a really nice web browsing experience at somewhat acceptable speed in SCREEN 2 (due to the FlyBrowser protocol in which is based). It uses a Intel x86 hosted proxy server called WILD (WWW Intelligent Lowsizer Daemon), that degraded the webpage to something that was possible for the MSX to manage.
Long ago I used to play with this browser and even hosted a publicly accessible WILD server. I still have some screenshots:
Anyway, I agree with the discussion so far: doing a text based web browser like Lynx or eLinks is almost the same as a graphical one, if you plan to render the HTML and CSS correctly even in text mode.
As mentioned here - HTTPS/TLS. There were questions and requests about GR8NET supporting these protocols, I personally is willing to implement them (partially within FPGA so performance will not be a bottleneck), but I need tech information what is required to support them. None so far approached me telling what computing power is required, and also for discussion how firmware/software architecture would look like.
Yay! That would be awesome. Sometimes we can't just download a file with HGET.COM or GR8NET basic program because the web is HTTPS, that is more and more common today. TLS proxy solutions are a pain for HTTP due to the certificate trust.
IIRC, GR8NET FPGA is an Altera Cyclone III right? That is the very same FPGA used by the Apollo Team in their next generation m68k CPU. I own that core on my Amiga and the speed is somewhat double of the 68060 at 50 MHz and mostly the same as a mid-range Pentium. In other words: it should be powerful enough to handle TLS. However, I guess that depends on the space available on the FPGA and the logic implementation; unless already done, I know this is quite hard. Also, my Amiga with Apollo Core handles SSH and TLS nicely due to the implementation of a fast m68k CPU, it's not using dedicated TLS encryption/decryption logic in the FPGA.
Maybe _NETBROWSE is exactly what this thread is asking for? 
@AxelStone @Wolverine_nl?
I will try to load a page using _netbrowse this evening. 
Very nice proof of concept! I'll try to understand the code, but asm is way too difficult for me yet..
I believe the browser should not require any external proxy and with basic html parsing (no images, etc) should be more than enough. I haven't tried _NETBROWSE so I don't know how it works, but it looks good.
I'll keep trying to implement something as a proof of concept too. No promises though