HTTP
IPFS
ZeroNet
thttpd
mini_httpd
micro_httpd
Solid
Gopher
StatusCake
UptimeRobot
Pingdom
Uptime Kuma
Better Uptime
Better Stack
Uptime.com
Site24x7
HTTP StatusCakeBusinesses of all sizes that need to ensure their websites are operational and performing well, IT professionals who require detailed monitoring and alerts, and anyone looking for a cost-effective and reliable monitoring solution with customizable features.
Based on our record, HTTP should be more popular than StatusCake. It has been mentiond 9 times since March 2021. 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 / almost 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
Statuscake.com if you just need a simple up/down monitor. Source: about 4 years ago
I've had a great time with statuscake.com for my personal and friends sites. They've even improved custom status pages to include an automatically signed certificate too, so you can make a site like status.yourdomain.com... Test TCP connection, specific HTTP/HTTPS query etc. 5 minute intervals for free, more with paid plans. Source: over 4 years ago
I use statuscake.com for external stuff and nagios for internal. PRTG is good too. Source: over 4 years ago
I use statuscake.com for all my personal / friend sites. There seems to be no limit to number of sites to monitor for basic 5 minute intervals in the free account. Source: almost 5 years ago
I use noip.com for a free domain name and a free plan on statuscake.com for this setup. Source: about 5 years ago
IPFS - IPFS is the permanent web. A new peer-to-peer hypermedia protocol.
UptimeRobot - Free Website Uptime Monitoring
ZeroNet - ZeroNet. Open, free and uncensorable websites, using Bitcoin cryptography and BitTorrent network. Download for Windows 9. 6MB ยท Unpack ยท Run ZeroNet. exe.
Pingdom - With website monitoring from Pingdom you will be the first to know when your website is down. No installation required. 30-day free trial.
thttpd - thttpd is a simple, small, portable, fast, and secure HTTP server.
Uptime Kuma - A fancy self-hosted monitoring tool.