3 ms·
It's a bigger issue than RSS, really. Fetching RSS is a simple GET request. It requires the most basic understanding of HTTP, and people still can't do it right
by troupo 2y ago
It's a bigger issue than RSS, really. Fetching RSS is a simple GET request. It requires the most basic understanding of HTTP, and people still can't do it right: they don't know how to deal with standard headers, how to deal with standard response codes, how to send proper requests etc.
Do you think regular REST API calls to any other service are any different?
- vallode 2y agoVery valid point, the frustrations here do share commonalities with the overall HTTP ecosystem.
- mimischi 2y agoAny pointers for good resources to grok best practices?
- vaylian 2y agoCache-Control goes a long way in the right direction: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Ca...
- troupo 2y agoNot sure about best practices, but these two resources are a good reference point: - Know Your HTTP Well: https://github.com/for-GET/know-your-http-well https://github.com/for-GET/know-your-http-well - HTTP Decision Diagram: https://github.com/for-GET/http-decision-diagram https://github.com/for-GET/http-decision-diagram