How vcr works, in a lot of detailsSource:
- Use either
- If you use
vcr::insert_cassette(), make sure to run
vcr::eject_cassette()when you’re done to stop recording
- When you first run a request with
vcrthere’s no cached data to use, so we allow HTTP requests until your request is done.
- Before we run the real HTTP request, we “stub” the request with
webmockrso that future requests will match the stub. This stub is an R6 class with details of the interaction (request + response), but is not on disk.
- After the stub is made, we run the real HTTP request.
- We then disallow HTTP requests so that if the request is done again we use the cached response
- The last thing we do is write the HTTP interaction to disk in a mostly human readable form.
When you run that request again using
- We use
webmockrto match the request to cached requests, and since we stubbed the request the first time we used the cached response.
Of course if you do a different request, even slightly (but depending on which matching format you decided to use), then the request will have no matching stub and no cached response, and then a real HTTP request is done - we then cache it, then subsequent requests will pull from that cached response.
webmockr has adapters for each R client (crul and httr) - so that we actually intercept HTTP requests when
webmockr is loaded and the user turns it on. So,
webmockr doesn’t actually require an internet or localhost connection at all, but can do its thing just fine by matching on whatever the user requests to match on. In fact,
webmockr doesn’t allow real HTTP requests by default, but can be toggled off of course.
The main use case we are going for in
vcr is to deal with real HTTP requests and responses, so we allow real HTTP requests when we need to, and turn it off when we don’t.
This gives us a very flexible and powerful framework where we can support
vcr integration for any number of R clients for HTTP requests and support many different formats serialized to disk.