This is continuation from part 1, where I present my thought process (rather, my internal dialogue) when troubleshooting a web issue.

Here we are, part 2 of digging into an issue discovered in a web browser. Using browser logs to analyze the API request & response behaviour, I can gain a better understanding of the issue.

Bonus: Something else I discovered during this exercise was that Safari allows you to provide a static response file to override an incoming API response.

I've been using Charles for years now and was pleasantly surprise by this native browser-based alternative. Read more here.