
HTTP
IPFS
ZeroNet
thttpd
mini_httpd
micro_httpd
Solid
Gopher
WireGuard
OpenVPN
ZeroTier
ProtonVPN
TailScale
Tor Browser
Hamachi
Psiphon
HTTP
WireGuardWireGuard might be a bit more popular than HTTP. We know about 9 links to it since March 2021 and only 9 links to HTTP. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
HTTP/1.1 was first published as RFC 2068 (The Proposed Standard) in January 1997. HTTP/1.1 protocol was refined over two revisions, RFC 2616 published in June 1999 and RFC 7230-RFC 7235 published in June 2014 before the release of HTTP/2. The HTTP/1.1 standard (RFC 2616) remained stable for over 15 years. In 2022, HTTP/1.1 was updated again with RFC 9110 & RFC 9112. - Source: dev.to / 9 months ago
HTTP was invented as a stateless protocol, which means that each request fully encapsulates all of the information necessary to return a correct response. So historically, web pages never had to worry about managing state - each request to a URL with parameters or with a form submission would receive a response with all of the HTML that the browser needed to render content. - Source: dev.to / about 2 years ago
HTTP/1.1 was such a game changer for the Internet that it works so well that even through two revisions, RFC 2616 published in June 1999 and RFC 7230โ RFC 7235 published in June 2014, HTTP/1.1 was extremely stable until the release of HTTP/2.0 in 2014โโโNearly 18 years later. Before continuing to the next section about HTTP/2.0, let us revisit what journey HTTP/1.1 has been through. - Source: dev.to / about 3 years ago
On the one hand, it just seems natural that "upstream" refers to the inbound request being sent from one system to another. It takes effort (connection pooling, throttling, retries, etc.) to make a request to an (upstream) dependency, just as it takes effort to swim upstream. The response is (usually) easy... Just return it... hence, "downstream". Recall the usual meaning of "upload" and "download". Upstream seems... - Source: Hacker News / over 4 years ago
To me it sounds like youโve not solved this as the config youโve mentioned is about preventing โillegalโ (none RFC7230 ) requests, it isnโt really related to the problem you posted. Source: over 4 years ago
Wireguard. Wireguard uses UDP only and runs TCP sockets over UDP. Source: about 3 years ago
Look at Wireguard. I know you don't want Yet Another VPN running alongside your IPSec, but it's less VPN and more encrypted point-to-point UDP. You can set it up on any port you wish, including common ports that might be open on an outbound smart firewall not doing deep packet inspection. That way, it can stay out of the way of your existing IPSec deployment. Source: about 3 years ago
We use Elixir/Erlang for our control plane, and Rust for our data plane, built on the excellent WireGuardยฎ tunneling protocol. Source: over 3 years ago
Both products are based off Wireguard which is available for all new linux distributions. https://wireguard.com . I'm not saying OP's solution is wrong, just curious what the advantages are. Other than potentially simpler client setup, what are the advantages of paying for tailscale. With the opensource tailscale, I'm not sure if you get access to an api you can use to look up the hosts. Source: over 3 years ago
Noise Protocol Framework (used by Wireguard). Source: over 3 years ago
IPFS - IPFS is the permanent web. A new peer-to-peer hypermedia protocol.
OpenVPN - OpenVPN - The Open Source VPN
ZeroNet - ZeroNet. Open, free and uncensorable websites, using Bitcoin cryptography and BitTorrent network. Download for Windows 9. 6MB ยท Unpack ยท Run ZeroNet. exe.
ZeroTier - Extremely simple P2P Encrypted VPN
thttpd - thttpd is a simple, small, portable, fast, and secure HTTP server.
ProtonVPN - ProtonVPN is a security focused FREE VPN service, developed by CERN and MIT scientists. Use the web anonymously, unblock websites & encrypt your connection.