Just realized the coffee shop wifi in Austin was quietly scanning my API test calls
I was at this spot on South Congress in Austin last week doing some endpoint testing on my laptop and something felt off. My calls kept coming back a little slow, like something was sitting in the middle of the connection. I pulled up the cert info and sure enough the shop's network was running a proxy that could see everything in plain text, including my bearer tokens. I had a test key in there for a sandbox account, so nothing real leaked, but it was way too close. The barista had no clue and honestly the owner probably doesn't either, they just plugged in whatever router the ISP handed them. The lesson I keep chewing on is that we lock down prod like a vault and then test with real-ish tokens on a random cafe network. Ten seconds of checking the cert saved me a headache. Has anyone found a good way to test this stuff on public wifi, or do you just tether off your phone and call it a day?
Yeah the cert trick is the move and honestly it's saved me more than once (I keep a little note on my phone reminding me to check before I type anything into a browser). What works for me is tethering off my phone for anything with real-ish tokens, no exceptions, and if I really need the cafe wifi I run everything through a VPN and skip the browser entirely. For sandbox stuff I'll sometimes spin up a throwaway key that expires in an hour so even if it leaks it's useless by lunch (the sandbox key thing bit me once, now I check expiry dates first). The other thing nobody mentions is turn off auto-connect on your laptop, because that saved network will hop on silently next time and you won't even think about it. Sounds like you caught it early, which is like 90% of the battle here.