Caching
Caching HTTP content correctly can be more challenging than necessary HARP Proxy built-in cache layer is designed to work out of the box with no configuration, with reasonable and conservative defaults to avoid unexpected issues. All its aspects are highly customizable to fit your specific needs: you can start in a breeze and slowly tune it to your requirements as you go.
Designed to integrate seamlessly with your existing infrastructure, using HARP's builtin cache system will save you time and resources that you don't want to spend on developing and maintaining your own caching solution. Focus on what truly matters: building great applications, not the technical details.
Works out of the box
You get a robust and reliable caching mechanism right out of the box, allowing to leverage sophisticated cache control strategies without the need for extensive configuration or in-depth knowledge of caching intricacies.
The underlying controller logic leverages the excellent Hishel library, which provides the base logic
library, which provides the base logic cache-control
(and other related headers) interpretation.
Standard-compliant
The behavior of HTTP caching is defined by the RFC-9111 standard, and HARP strictly adheres to these standards. This ensures that our caching mechanisms are reliable, predictable, and compatible with other systems. By following these guidelines, HARP provides a robust caching solution that aligns with industry best practices, giving you confidence in its performance and compliance.
Industry standard test suite
To ensure that our system works as expected, we use the Tests for HTTP Caches suite as our benchmark to gauge the effectiveness of our caching solution. This rigorous testing helps us achieve near browser-grade cache behavior, ensuring that HARP's caching system is both reliable and performant. By adhering to these industry-standard tests, we provide a robust and dependable caching solution that meets high-quality standards.
Customizable at will
One goal of HARP is to be as plug and play as possible, another one is to enpower you with a swiss-army knife to «fix the internet», or at least some of those bad APIs you're using. Your remote service does not comply with HTTP? Defined its own headers? Sends cache-control headers that force cache of uncacheable content? No problem, we got you covered.
rules: "*": "GET /v2/*": on_http_response: response.headers["cache-control"] = "public, max-age=3600"
Do not worry about the rules engine limits. It's just Python! If you can code it, HARP can do it. And even if Python is not your favorite language, most of the tuning rules are simple assignations and tests, we're pretty sure you can handle it.