HTTP, REST & APIs
Methods, status codes, statelessness, and what a cookie is really for.
0 of 23 answered
Start here
GET or POST
Foundation
- Not triedGET or POSTFoundation
- Not triedNaming a REST endpointFoundation
- Not triedReading a status codeFoundation
- Not triedReusing the connectionFoundation
- Not triedTelling a client to slow downFoundation
- Not triedWhat HTTPS actually protectsFoundation
- Not triedWhat stateless meansFoundation
- Not triedAsking whether it changedCore
- Not triedChoosing between POST and PUTCore
- Not triedPermanent or temporaryCore
- Not triedTelling a cache what to doCore
- Not triedWhat a 500 does and does not tell youCore
- Not triedWhat HTTP/2 fixedCore
- Not triedWhere the session livesCore
- Not triedWhich status code is a lieCore
- Not triedWhy PUT is idempotent and POST is notCore
- Not triedChanging an API without breaking clientsChallenge
- Not triedRevalidation is not the same as cachingChallenge
- Not triedSending a response of unknown lengthChallenge
- Not triedSigning out a token that cannot be recalledChallenge
- Not triedThe request timed out. Retry it?Challenge
- Not triedWhat HTTP/2 fixed and what it did notChallenge
- Not triedWhy the browser blocked the requestChallenge