The End of http.sh

I noticed that http.sh, one of my early projects, had been taken offline (archive). It first launched in 2008. You gave it a web page or script and a schedule, and it requested that page on time, so it could check that a site was up or hit a scheduling endpoint. At its peak it ran requests for more than 800 websites.

The customer wanted the scheduler written as a multithreaded Linux daemon in C, and I delivered.

What It Did

• GET and POST requests.
• HTTP and HTTPS.
• A report on each request: IP resolution errors, header size, header time and speed, and the HTTP status code.
• Most cron schedules. Every 1, 5, 10, 15. or 30 minutes; every 1, 2, 4, 6, or 12 hours; daily, or on a day of the week; or on the 1st or 15th of the month.