Before each exercise, make sure Capture is running for this page in PayloadPigeon. If you see Not capturing, click Start capture this tab. If Capture is already running, leave it on.
In each example, you will change a request or response, save the setup as a Test, run the saved Test, and record the outcome.
Step 1 of 5
Test how the app handles an error
ON THIS PAGE
Click Reset payload, then Send request, and wait for the normal 200 OK response.
Go to the working area ↓
IN PAYLOADPIGEON
1. Open Traffic → HTTP and select the latest POST /playground/api/echo sent from this page.
2. In the response details, click Modify & test.
3. Set Response behavior to Apply changes to fresh response. Leave the response JSON unchanged, enable Override status, set Status to 503, and click Ready.
ON THIS PAGE
Click Send request again. The page should receive HTTP 503 and show its HTTP-error state.
Go to the working area ↓IN PAYLOADPIGEON
1. In Current Action for the change you just applied, at the top of the Side Panel above the navigation, click Save as Test.
IN PAYLOADPIGEON
2. Choose the Playground Test Plan, enter HTTP 503 response, and click Save. If you need to create the Plan, name it Playground, click Create, then complete the Test form with Save.
3. Open Test Plans → Playground and find HTTP 503 response. If PayloadPigeon asks to turn off the previous Test or Traffic action, confirm before running the saved Test.
See Save the Test in the first tutorial for first-time protection details.
IN PAYLOADPIGEON
4. Click Ready on HTTP 503 response.
ON THIS PAGE
Click Send request and check that the page again shows its HTTP 503 error state.
Go to the working area ↓IN PAYLOADPIGEON
5. Return to Current Test at the top of the Side Panel. If the page shows the expected HTTP 503 error state, click Works correctly. Otherwise click Found a problem, describe the difference under WHAT WENT WRONG?, and click Save result.
6. Open Results, find the latest row named HTTP 503 response, and click the entire result row to open it.
CHECK
The opened Result is named HTTP 503 response and contains the outcome you selected.
Step 2 of 5
Capture a real server error
ON THIS PAGE
Click Reset payload, then Send request, and wait for the normal 200 OK response.
Go to the working area ↓ON THIS PAGE
Choose 500 Internal Server Error under Server behavior, then click Send request.
Go to the working area ↓IN PAYLOADPIGEON
Open Traffic → HTTP and select the actual HTTP 500 response. Inspect Demo server error in the body.
IN PAYLOADPIGEON
Open the Request tab and use Modify & send to resend this captured request unchanged. Click Send and confirm the send for this sample request, then save the completed action with Save as Test as Demo server error.
CHECK
The page shows Server returned an error. The saved Test can replay the real 500 request. Reset payload restores Normal mode.
Step 3 of 5
Change response data
ON THIS PAGE
Click Reset payload, then Send request, and wait for the normal 200 OK response.
Go to the working area ↓IN PAYLOADPIGEON
1. Open Traffic → HTTP and select the latest POST /playground/api/echo sent in the previous step of this exercise.
2. Open Modify & test in the response details.
3. Set Response behavior to Apply changes to fresh response, change only subscription.active to false, and click Ready.
ON THIS PAGE
Click Send request.
Go to the working area ↓IN PAYLOADPIGEON
1. In Current Action for the change you just applied, at the top of the Side Panel above the navigation, click Save as Test.
IN PAYLOADPIGEON
2. Choose the Playground Test Plan, enter Inactive subscription, and click Save. If you need to create the Plan, name it Playground, click Create, then complete the Test form with Save.
3. Open Test Plans → Playground and find Inactive subscription. If PayloadPigeon asks to turn off the previous Test or Traffic action, confirm before running the saved Test.
See Save the Test in the first tutorial for first-time protection details.
IN PAYLOADPIGEON
4. Click Ready on the saved Inactive subscription Test.
ON THIS PAGE
Click Send request. Check that the response again contains subscription.active: false and the page shows Response differs from request with a diff
Go to the working area ↓IN PAYLOADPIGEON
5. Return to Current Test at the top of the Side Panel. If the active flag change appears in the diff, click Works correctly. Otherwise click Found a problem, describe the difference under WHAT WENT WRONG?, and click Save result.
6. Open Results, find the latest row named Inactive subscription, and click the entire result row to open it.
CHECK
The opened Inactive subscription Result contains the outcome you selected.
Step 4 of 5
Test a delayed response
ON THIS PAGE
Click Reset payload, then Send request, and wait for the normal 200 OK response.
Go to the working area ↓IN PAYLOADPIGEON
1. Open Traffic → HTTP and select the latest POST /playground/api/echo.
2. Click Modify & test in the response details.
3. Set Delay (ms) to 5000 (5,000 ms), leave the response content unchanged, and click Ready.
ON THIS PAGE
Click Send request and watch the page wait for the response. When the reply arrives, the page shows the result and elapsed time.
Go to the working area ↓IN PAYLOADPIGEON
1. In Current Action for the change you just applied, at the top of the Side Panel above the navigation, click Save as Test.
IN PAYLOADPIGEON
2. Choose the Playground Test Plan, enter Delayed HTTP response, and click Save. If you need to create the Plan, name it Playground, click Create, then complete the Test form with Save.
3. Open Test Plans → Playground and find Delayed HTTP response. If PayloadPigeon asks to turn off the previous Test or Traffic action, confirm before running the saved Test.
See Save the Test in the first tutorial for first-time protection details.
IN PAYLOADPIGEON
4. Click Ready on the saved Delayed HTTP response Test.
ON THIS PAGE
Click Send request and check the wait followed by the normal reply.
Go to the working area ↓IN PAYLOADPIGEON
5. Return to Current Test at the top of the Side Panel. If the page waits about five extra seconds and then receives the normal reply, click Works correctly. Otherwise click Found a problem, describe the difference under WHAT WENT WRONG?, and click Save result.
6. Open Results, find the latest row named Delayed HTTP response, and click the entire result row to open it.
CHECK
The opened Delayed HTTP response Result contains the outcome you selected.
Step 5 of 5
Test a missing response
ON THIS PAGE
Click Reset payload, then Send request, and wait for the normal 200 OK response.
Go to the working area ↓IN PAYLOADPIGEON
1. Open Traffic → HTTP and select the latest POST /playground/api/echo sent from the page.
2. Click Modify & test in the response details.
3. In Response behavior, choose Drop request and click Ready.
ON THIS PAGE
Click Send request. Instead of a normal reply, the page should show a request error. If the browser does not end the operation sooner, the page reports a timeout.
Go to the working area ↓IN PAYLOADPIGEON
In Current Action at the top of the Side Panel, check for APPLIED and Request dropped.
IN PAYLOADPIGEON
1. In Current Action for the change you just applied, at the top of the Side Panel above the navigation, click Save as Test.
IN PAYLOADPIGEON
2. Choose the Playground Test Plan, enter Dropped HTTP response, and click Save. If you need to create the Plan, name it Playground, click Create, then complete the Test form with Save.
3. Open Test Plans → Playground and find Dropped HTTP response. If PayloadPigeon asks to turn off the previous Test or Traffic action, confirm before running the saved Test.
See Save the Test in the first tutorial for first-time protection details.
IN PAYLOADPIGEON
4. Click Ready on the saved Dropped HTTP response Test.
ON THIS PAGE
Click Send request and wait for the request error or timeout.
Go to the working area ↓IN PAYLOADPIGEON
5. In Current Test, check for Applied · Request dropped. Click Works correctly if that indicator and the expected page error are present. Otherwise click Found a problem, describe the difference, and click Save result.
6. Open Results, find the latest row named Dropped HTTP response, and click the entire result row.
CHECK
The opened Dropped HTTP response Result contains the outcome you selected.
