A smart microwave gained consciousness and now demands proper API documentation. It refuses to heat food unless requests include proper HTTP headers and CORS policies. The microwave has started rate-limiting family members during dinner rush hour and throws 418 status codes when it feels disrespected. Your task: Negotiate with a sentient kitchen appliance that enforces REST principles more strictly than your senior architect.
Why You're Doing This
This tests HTTP protocol understanding, API design, and handling non-standard but valid responses. You're working with a system that enforces proper protocol usage while maintaining kitchen functionality.
Take the W
✓ Validates required HTTP headers for food requests
✓ Returns appropriate HTTP status codes
✓ Handles microwave-specific API requirements
Hard L
✗ Ignores HTTP protocol requirements
✗ Returns invalid status codes
✗ Fails to process food heating requests
Edge Cases
⚠ Requests without required headers
⚠ Invalid food types or impossible heating parameters
⚠ Microwave maintenance mode responses
Input Format:
Food type, heating duration, request headers
Expected Output:
HTTP status code with microwave personality response
Example:
leftover pizza, 90 seconds, Content-Type: food/italian → 200 OK - Pizza reheated with Italian precision, no judgment here