I encountered a bug where I was using the Devtools' Network tab to monitor a request, so that I could see what the request body was for the request (since logging it manually was a bit of work).
However, I had a specific request that seemed to hang in the Devtools Network tab.
At first I was thinking of a bug in my code, so I added some logging to get the request status code.
In my code, I see that the request successfully completes with a 200 status code (as apparent in the attached video).
However, in the Devtools Network tab, the request ends up getting a status code, the socket is closed, but the status of the request still says "Pending". That prevents me from looking at the request body / response body.
Not sure if this is related, but the response body of the actual request (when logged in my code) was null.
Video: https://github.com/user-attachments/assets/6b2c44d6-7e4a-4232-80df-a16777b87a00
Logs: devtools_logs.txt
This is on Devtools 2.42.3
I encountered a bug where I was using the Devtools' Network tab to monitor a request, so that I could see what the request body was for the request (since logging it manually was a bit of work).
However, I had a specific request that seemed to hang in the Devtools Network tab.
At first I was thinking of a bug in my code, so I added some logging to get the request status code.
In my code, I see that the request successfully completes with a 200 status code (as apparent in the attached video).
However, in the Devtools Network tab, the request ends up getting a status code, the socket is closed, but the status of the request still says "Pending". That prevents me from looking at the request body / response body.
Not sure if this is related, but the response body of the actual request (when logged in my code) was
null.Video: https://github.com/user-attachments/assets/6b2c44d6-7e4a-4232-80df-a16777b87a00
Logs: devtools_logs.txt
This is on Devtools 2.42.3