The recording for episode #3 is now available on Crowdcast and YouTube. In this episode we cover issues like API description languages, security weaknesses in HTTP APIs and the illusive HTTP status code 410 Gone.
![Glenn Miller Loved HTTP](https://e3c4fpsheba.exactdn.com/wp-content/uploads/2022/12/BIGglennmiller-1.jpeg?strip=all&lossy=1&resize=529%2C410&ssl=1)
Some of the questions we attempted to answer this week include:
- What is your take on things like Swagger? Didn’t we learn our lessons with WSDL?
- What are the biggest security flaws on HTTP API designs and implementations you are seeing quite often?
- Is there any advantage of returning HTTP status code 410 rather than 404?
- I have an API that needs to scale. I can add HTTP caches and load balancers. Will using a message bus on the server help?
- Those days looks like REST and JSON are strictly correlated, I would love to hear you demistify this and introduce content negotiation.
Links from the show include:
- Prefer header : https://tools.ietf.org/html/rfc7240
- 410 Gone : https://tools.ietf.org/html/rfc7231#section-6.5.9
- WADL: https://www.w3.org/Submission/wadl/
- Swagger: https://swagger.io/
- RAML: https://raml.org/
- API Blueprint: https://apiblueprint.org/
- Collection+JSON: http://amundsen.com/media-types/collection/
- HAL: https://stateless.group/hal_specification.html
Keep your eyes on our twitter accounts @darrel_miller and @gblock for the announcement of our next episode and get your questions ready!