From 10efdf58f583336eda5eb7960e013a7fab451807 Mon Sep 17 00:00:00 2001 From: yi-gu Date: Tue, 7 May 2024 15:11:23 -0400 Subject: [PATCH] Update debug-network-requests-chrome.md fix image links --- explorations/debug-network-requests-chrome.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/explorations/debug-network-requests-chrome.md b/explorations/debug-network-requests-chrome.md index 1f248440..e64b0ad2 100644 --- a/explorations/debug-network-requests-chrome.md +++ b/explorations/debug-network-requests-chrome.md @@ -3,27 +3,27 @@ While the Chrome team is trying to integrate FedCM into devtools, we suggest dev 1. Open chrome://net-export from the URL bar. Select “Include raw bytes” and click “Start Logging to Disk”. Select a location to save the logs when prompted.

- +

2. Open the page that calls the FedCM API. e.g. https://webid-fcm.glitch.me

- +

3. Go through the FedCM flow to debug all network requests

- +

4. Stop the logging on chrome://net-export

- +

5. Load the logs into https://netlog-viewer.appspot.com/

- +

6. Under `Events` from the left, filter the logs with `type:URL_REQUEST`

- +

7. The network requests that were sent to different endpoints can be viewed individually. They also include the response that the browser has received. If