Contents

---
http_interactions:
- request:
    method: get
    uri: https://develop.lifen.fr/fhir/Communication/non_valid_communication_uuid
    body:
      encoding: UTF-8
      string: "{}"
    headers:
      User-Agent:
      - Faraday v0.12.1
      Authorization:
      - Bearer valid_application_access_token
      Accept:
      - application/json
      Accept-Encoding:
      - gzip;q=1.0,deflate;q=0.6,identity;q=0.3
  response:
    status:
      code: 404
      message: Not Found
    headers:
      Server:
      - Apache-Coyote/1.1
      X-B3-Traceid:
      - d25962660c460cd1
      X-B3-Spanid:
      - d25962660c460cd1
      X-Content-Type-Options:
      - nosniff
      X-Xss-Protection:
      - 1; mode=block
      Cache-Control:
      - no-cache, no-store, max-age=0, must-revalidate
      Pragma:
      - no-cache
      Expires:
      - '0'
      X-Powered-By:
      - HAPI FHIR 2.4 REST Server (FHIR Server; FHIR 3.0.1/DSTU3)
      Content-Type:
      - application/json+fhir;charset=UTF-8
      Transfer-Encoding:
      - chunked
      Date:
      - Tue, 06 Jun 2017 11:51:14 GMT
      Access-Control-Allow-Credentials:
      - 'true'
    body:
      encoding: UTF-8
      string: |-
        {
          "resourceType": "OperationOutcome",
          "issue": [
            {
              "severity": "error",
              "code": "not-found",
              "diagnostics": "Unknown Resource id=non_valid_communication_uuid"
            }
          ]
        }
    http_version:
  recorded_at: Tue, 06 Jun 2017 11:50:35 GMT
recorded_with: VCR 3.0.3

Version data entries

2 entries across 2 versions & 1 rubygems

Version	Path
lifen_fhir-0.7.1	spec/cassettes/communication/find_by_uuid/non_valid_uuid.yml
lifen_fhir-0.7.0	spec/cassettes/communication/find_by_uuid/non_valid_uuid.yml