cachedPOST

additional arguments passed to the httr functions

Some APIs have resources where a POST is used to send a command that returns
content and doesn't modify state. In this case, it's more like a GET. This
may occur where one might normally GET but the request URI would be too long
for the server to accept. <code>cachedPOST</code> thus behaves more like
<code>GET</code>, checking for a cached response before performing the request and
setting cache if the request is successful. It does no cache dropping, unlike
<code><a rd-options="=POST" href="/link/POST()?package=httpcache&version=1.2.0&to=%3DPOST" data-mini-rdoc="=POST::POST()">POST()</a></code>.

In order to improve performance for HTTP API clients, 'httpcache'
provides simple tools for caching and invalidating cache. It includes the
HTTP verb functions GET, PUT, PATCH, POST, and DELETE, which are drop-in
replacements for those in the 'httr' package. These functions are cache-aware
and provide default settings for cache invalidation suitable for RESTful
APIs; the package also enables custom cache-management strategies.
Finally, 'httpcache' includes a basic logging framework to facilitate the
measurement of HTTP request time and cache performance.

Neal Richardson

httpcache

Query Cache for HTTP Clients

cachedPOST function

Some APIs have resources where a POST is used to send a command that returns
content and doesn't modify state. In this case, it's more like a GET. This
may occur where one might normally GET but the request URI would be too long
for the server to accept. <code>cachedPOST</code> thus behaves more like
<code>GET</code>, checking for a cached response before performing the request and
setting cache if the request is successful. It does no cache dropping, unlike
<code><a rd-options='=POST' href='POST()'>POST()</a></code>.

cachedPOST: Cache the response of a POST

Description

Usage

Arguments

Value