NASA’s new dark energy space telescope can also detect killer asteroids
technologyreview.com·2h ago
Data Science
Towards AI·23d ago·5 min read
HTTP Has a New Method Now (After 16 Years!), and it lands where AI agents were bleeding
TL;DR
HTTP has introduced a new method called QUERY, which allows for body-carrying requests while maintaining safety and idempotence. This method addresses the long-standing issue of using POST for read-only searches that exceed URL length limits.
✦ Why It Matters
Engineers should adopt the QUERY method for large read-only requests to improve caching and proxy interactions in their applications.
Key Takeaways
- Implement the QUERY method for large read-only searches.
- Avoid using POST for non-modifying requests to improve caching.
- Update existing systems to support the new QUERY method.
- Educate teams on the implications of safe and idempotent methods.
Full Summary
For the first time in 16 years, HTTP has added a new method, QUERY, as defined in RFC 10008. This method allows requests to carry a body like POST but remains safe and idempotent like GET, meaning it does not alter server state and can be repeated without side effects.
QUERY effectively replaces a decade-old workaround where large read-only searches were incorrectly sent as POST requests, misleading caches and proxies. The introduction of QUERY aims to improve the handling of large queries, ensuring they are cacheable and correctly interpreted by intermediaries.
This change is particularly relevant for AI agents that often perform extensive data retrieval, as it mitigates issues related to request size and caching. By clarifying the intent of read-only operations, QUERY enhances the overall efficiency and reliability of web applications.