# Matching on URI

Use the `:uri` request matcher to match requests on the request URI.

The `:uri` matcher is used (along with the `:method` matcher) by default if you do not specify how requests should match.

## Background ()

*Given* a previously recorded cassette file "cassettes/example.yml" with:

```
--- 
http_interactions: 
- request: 
    method: post
    uri: http://example.com/foo
    body: 
      encoding: UTF-8
      string: ""
    headers: {}
  response: 
    status: 
      code: 200
      message: OK
    headers: 
      Content-Length: 
      - "12"
    body: 
      encoding: UTF-8
      string: foo response
    http_version: "1.1"
  recorded_at: Tue, 01 Nov 2011 04:58:44 GMT
- request: 
    method: post
    uri: http://example.com/bar
    body: 
      encoding: UTF-8
      string: ""
    headers: {}
  response: 
    status: 
      code: 200
      message: OK
    headers: 
      Content-Length: 
      - "12"
    body: 
      encoding: UTF-8
      string: bar response
    http_version: "1.1"
  recorded_at: Tue, 01 Nov 2011 04:58:44 GMT
recorded_with: VCR 2.0.0
```

## Replay interaction that matches the request URI

*And* a file named "uri\_matching.rb" with:

```
include_http_adapter_for("<http_lib>")

require 'vcr'

VCR.configure do |c|
  <configuration>
  c.cassette_library_dir = 'cassettes'
end

VCR.use_cassette('example', :match_requests_on => [:uri]) do
  puts "Response for /bar: " + response_body_for(:get, "http://example.com/bar")
end

VCR.use_cassette('example', :match_requests_on => [:uri]) do
  puts "Response for /foo: " + response_body_for(:get,  "http://example.com/foo")
end
```

*When* I run `ruby uri_matching.rb`

*Then* it should pass with:

```
Response for /bar: bar response
Response for /foo: foo response
```

### Examples

| configuration          | http\_lib              |
| ---------------------- | ---------------------- |
| c.hook\_into :webmock  | net/http               |
| c.hook\_into :webmock  | httpclient             |
| c.hook\_into :webmock  | curb                   |
| c.hook\_into :webmock  | patron                 |
| c.hook\_into :webmock  | em-http-request        |
| c.hook\_into :webmock  | typhoeus               |
| c.hook\_into :typhoeus | typhoeus               |
| c.hook\_into :excon    | excon                  |
| c.hook\_into :faraday  | faraday (w/ net\_http) |
| c.hook\_into :faraday  | faraday (w/ typhoeus)  |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://andrewmcodes.gitbook.io/vcr/request_matching/uri.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.