Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create debug-network-requests-chrome.md #573

Merged
merged 2 commits into from
May 7, 2024
Merged

Create debug-network-requests-chrome.md #573

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f6d9c6c
Create debug-network-requests-chrome.md
yi-gu May 7, 2024
3cd3a44
Update debug-network-requests-chrome.md
yi-gu May 7, 2024
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update debug-network-requests-chrome.md 
address comments
  • Loading branch information
@yi-gu
yi-gu committed May 7, 2024
commit 3cd3a44f733bc08e527209499b255ba10d6a94ed
20 changes: 12 additions & 8 deletions explorations/debug-network-requests-chrome.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,27 +1,31 @@
While the Chrome team is trying to integrate FedCM into devtools, we suggest developers to use the following tools to debug network requests.

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.
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.
<p align="center">
<img width="467" src="https://github.com/yi-gu/fedcm-images/blob/main/net-export/net-export-entry.png?raw=true"/>
<img width="467" src="https://github.com/fedidcg/FedCM/blob/main/explorations/static/net-export/net-export-entry.png?raw=true"/>
</p>
2. Open the page that calls the FedCM API. e.g. https://webid-fcm.glitch.me
<p align="center">
<img width="467" src="https://github.com/yi-gu/fedcm-images/blob/main/net-export/fedcm-1.png?raw=true"/>
<img width="467" src="https://github.com/fedidcg/FedCM/blob/main/explorations/static/net-export/fedcm-1.png?raw=true"/>
</p>
3. Go through the FedCM flow to debug all network requests
<p align="center">
<img width="467" src="https://github.com/yi-gu/fedcm-images/blob/main/net-export/fedcm-2.png?raw=true"/>
<img width="467" src="https://github.com/fedidcg/FedCM/blob/main/explorations/static/net-export/fedcm-2.png?raw=true"/>
</p>
4. Stop the logging on chrome://net-export
<p align="center">
<img width="467" src="https://github.com/yi-gu/fedcm-images/blob/main/net-export/net-export-stop.png?raw=true"/>
<img width="467" src="https://github.com/fedidcg/FedCM/blob/main/explorations/static/net-export/net-export-stop.png?raw=true"/>
</p>
5. Load the logs into https://netlog-viewer.appspot.com/
<p align="center">
<img width="467" src="https://github.com/yi-gu/fedcm-images/blob/main/net-export/netlog-viewer-entry.png?raw=true"/>
<img width="467" src="https://github.com/fedidcg/FedCM/blob/main/explorations/static/net-export/netlog-viewer-entry.png?raw=true"/>
</p>
6. Under `Events` from the left, filter the logs with `type:URL_REQUEST`
<p align="center">
<img width="467" src="https://github.com/yi-gu/fedcm-images/blob/main/net-export/netlog-viewer-example.png?raw=true"/>
<img width="467" src="https://github.com/fedidcg/FedCM/blob/main/explorations/static/net-export/netlog-viewer-example.png?raw=true"/>
</p>
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 raw bytes are selected from step 1, the detailed response such as name, token string etc. will show up on the right.
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
raw bytes are selected from step 1, the detailed response such as name, token
string etc. will show up on the right.
Loading