Four tools I reach for when a request misbehaves. I test the pattern before I paste it into code. I decode the URL before I blame the service. I build the curl by hand once, then I read it back to check what it really sends. That is the whole job here. Nothing leaves this page.
I type a pattern, I paste the text, I see every match light up. I wrote a bad pattern at 2 AM once and shipped it. This is where I catch it now, before it ships.
Matches highlighted
Match details and capture groups
A space in a query string broke a deploy for me once. The service saw a different URL than I sent. I encode first and read the result before I paste it anywhere.
Result
I fill in the method, the URL, the headers and the body. The tool writes the curl command for me, with the quoting done right. I copy it into my terminal and I know what it will send.
Curl command
Someone pastes a long curl command in a chat at midnight and I need to know what it does before I run it. I paste it here and read the method, the URL, the headers and the body as plain lines.
Breakdown