TINYLAB
TINYLAB DEV
🌐 RFC PROTOCOL CHALLENGE+200 XP BADGE REWARD

WHICH HTTP CODE IS IT?

Put your web protocol knowledge to the test. Read real-world backend API and browser scenarios and pick the exact IETF RFC status code!

SCENARIO 1 OF 10SCORE: 0 CORRECT
SCENARIO #1

A client sends a request to brew coffee using an automated Hyper Text Coffee Pot Control Protocol (HTCPCP), but the server is permanently a teapot.

HOW IT WORKS & METHODOLOGY

UNDERSTANDING THE MATH, FORMULAS & CALCULATION ENGINE

01

Read Real API Scenarios

Examine real-world backend microservice errors, rate limiting conditions, idempotent conflicts, and RFC edge cases.

02

Select the RFC Compliant Code

Pick the exact 3-digit status code that matches the IETF / RFC standard specification.

03

Claim RFC Certification

Score points, read the official RFC spec quotes, and generate an authenticated RFC 9110 HTTP Master certificate.

FREQUENTLY ASKED QUESTIONS

EVERYTHING YOU NEED TO KNOW ABOUT THIS EXPERIMENT

Q1.What is the difference between 401 Unauthorized and 403 Forbidden?
401 Unauthorized indicates unauthenticated access (missing or invalid credentials; authentication is required). 403 Forbidden means the server understands who you are, but you lack permission to access the resource.
Q2.What is 418 I'm a teapot?
Defined originally in RFC 2324 as an April Fools joke for the Hyper Text Coffee Pot Control Protocol (HTCPCP), 418 was codified into RFC 9110 as a reserved status code and beloved developer easter egg.
Q3.What is the difference between 502 Bad Gateway and 504 Gateway Timeout?
A 502 means an upstream server returned an invalid response to the proxy/reverse proxy. A 504 means the upstream server failed to respond within the gateway timeout window.