如何获取Chrome发送的原始HTTP请求字符串？求调试工具推荐

Great question! When building an HTTP request parser, having access to raw, unprocessed request strings is critical for testing edge cases, weird header formats, and real-world request patterns. Let’s break this down into two parts: grabbing raw requests directly from Chrome, and alternative tools if you need more test data.

Getting Raw HTTP Requests from Chrome #

Chrome doesn’t show raw request strings directly in the Network tab, but there are workarounds to extract them:

1. Use cURL Copy + Trace #

This is probably the quickest method for individual requests:

• Open Chrome DevTools (hit F12 or Ctrl+Shift+I), switch to the Network tab.
• Refresh the page and find the request you want to inspect (click on it to see details).
• Right-click the request, select Copy > Copy as cURL (bash).
• Paste the copied command into your terminal, then add --trace-ascii - at the end. For example:

  curl 'https://example.com' -H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36...' --trace-ascii -
  

  Run the command, and you’ll see the full raw HTTP request (headers, method, path, and body if present) in the output.

2. Chrome NetLog #

For capturing multiple requests at once, Chrome’s NetLog logs all network activity including raw request data:

• In Chrome’s address bar, go to chrome://net-export/.
• Click Start logging to disk and choose where to save the log file.
• Navigate to the website or trigger the requests you want to capture, then go back to chrome://net-export/ and click Stop logging.
• You can parse the JSON log file to extract raw request details—look for entries with type: "HTTP_REQUEST_HEADERS" and type: "HTTP_REQUEST_BODY"; combining these will give you the full raw request string.

3. Network Packet Capture (Wireshark) #

If you want the absolute raw bytes Chrome sends, use a packet sniffer like Wireshark:

• Open Wireshark, select your active network interface (e.g., WiFi or Ethernet).
• For HTTP (non-encrypted), set a filter: http or tcp port 80.
• For HTTPS, you’ll need to decrypt traffic first:
  1. Set the environment variable SSLKEYLOGFILE to a file path on your system (e.g., SSLKEYLOGFILE=C:\sslkeys.log on Windows, export SSLKEYLOGFILE=~/sslkeys.log on macOS/Linux).
  2. Restart Chrome, then in Wireshark go to Edit > Preferences > Protocols > TLS and set the "(Pre)-Master-Secret log filename" to your SSLKEYLOGFILE path.
• Once set up, you’ll see the decrypted raw HTTP requests in Wireshark’s packet details.

Tools/Resources for Mock HTTP Requests #

If you need a large volume of test requests (or want to simulate edge cases Chrome might not generate), these options work well:

• cURL: You can manually construct any type of request (POST with JSON body, custom headers, PUT requests, etc.) and use --trace-ascii to get the raw string. Example of a POST request:

  curl -X POST 'https://example.com/api/submit' -H 'Content-Type: application/json' -d '{"username":"test","password":"1234"}' --trace-ascii -
  

• HTTPie: A more user-friendly alternative to cURL. Use the --verbose flag to see the raw request sent:

  http POST https://example.com/api/submit username=test password=1234 --verbose
  

• Mockaroo: Generate bulk mock requests with varying headers, methods, and body formats (JSON, form-data, plain text). You can customize fields to match real-world scenarios (e.g., different User-Agents, auth tokens).
• Local Mock Servers: Build a simple server with Node.js/Express or Python/Flask that logs every incoming request. For example, with Express:

  const express = require('express');
  const app = express();
  app.use(express.text({ type: '*/*' }));
  
  app.all('*', (req, res) => {
    // Construct raw request string
    const rawRequest = `${req.method} ${req.url} HTTP/${req.httpVersion}\n` +
      Object.entries(req.headers).map(([key, value]) => `${key}: ${value}`).join('\n') +
      '\n\n' + req.body;
    console.log(rawRequest);
    res.send('OK');
  });
  
  app.listen(3000, () => console.log('Mock server running on port 3000'));
  

  Send requests to http://localhost:3000 and the server will print the full raw request.
• Open Source Request Samples: Search GitHub for "HTTP request samples" to find repositories with hundreds of real-world requests (including edge cases like malformed headers, multi-part forms, and unusual encoding).

内容的提问来源于stack exchange，提问作者User1337