@replayio-app-building/netlify-recorder 0.15.7 → 0.15.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -113,7 +113,7 @@ export default createRecordingRequestHandler(
|
|
|
113
113
|
|
|
114
114
|
> **Note:** Always use the response returned by the wrapper (or `finishRequest`), not your original response object. The wrapper adds the `X-Replay-Request-Id` header to the response it returns.
|
|
115
115
|
|
|
116
|
-
###
|
|
116
|
+
### 3. Create recordings
|
|
117
117
|
|
|
118
118
|
When you want to turn a captured request into a Replay recording, POST to the service's `create-recording` endpoint with the request ID. If the request was created with a secret, you must include it:
|
|
119
119
|
|
|
@@ -146,7 +146,7 @@ On failure:
|
|
|
146
146
|
{ "status": "failed", "error": "Error message" }
|
|
147
147
|
```
|
|
148
148
|
|
|
149
|
-
###
|
|
149
|
+
### 4. Check recording status
|
|
150
150
|
|
|
151
151
|
You can poll the recording status at any time. If the request was created with a secret, you must include it:
|
|
152
152
|
|
|
@@ -161,7 +161,7 @@ const { status, recordingId } = await res.json();
|
|
|
161
161
|
|
|
162
162
|
Requests created with a secret return 403 if the secret is missing or incorrect.
|
|
163
163
|
|
|
164
|
-
###
|
|
164
|
+
### 5. Access control with secrets
|
|
165
165
|
|
|
166
166
|
You can restrict access to captured requests by setting a `secret` string. When a secret is set, the request is only accessible via API calls that provide the same secret value. This lets each app isolate its requests from other apps sharing the same Netlify Recorder service.
|
|
167
167
|
|