HTTP Status as a Service: A quick and (maybe) dumb idea

Lee Gillentine
Jun 5, 2018 · 1 min read
Image for post
Image for post
A micro-product to solve my own problem

Status.icu is a simple product I built to solve a problem I was having while running some automated headless browser tests. I was also looking to have some fun with CSS Grid and building a product landing page.

The problem: In my test environment, I’m making http requests to urls based on data from Faker. Imagine a profile page that displays a profile picture based on an email address — like <img src="https://gravatar.org?email=fake.name@fake.com"/>.

When your automated browser hits that page, you obviously don’t want it to make a request to gravatar.org. With status.icu, you can prepend that url and get back a simple 200. It can look like this: <img src= "https://status.icu/200https://gravatar.org?email=fake.name@fake.com" />. Now your automated tests won’t be littering logs on 3rd party URLs.

On-demand HTTP status codes might also be useful when rapidly prototyping an API or testing out responses to different HTTPs statuses.

Status.icu supports blindly returning a variety of status codes, including 201, 404, 422, and 500.

Is this useful to anyone else? Let me know in the comments!

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store