如何获取Web应用中有效页面间带参数的跳转路径？

Great question! Let’s walk through practical ways to map out these parameterized page paths in your web app, using your specific example as a guide.

This is perfect if you want a quick, hands-on understanding of the flow:

• Start at login.php: Enter a test username and password, then submit the form. Note the jump to index.php, and whether the parameters are visible in the URL (GET method) or hidden (POST method).
• Next, on index.php: Input a numeric product_id and submit. Observe the redirect to product.php, and confirm how product_id is passed (again, check the URL for GET parameters, or note if it’s sent via POST).
• Document the full chain as you go: login.php (params: username, password) → index.php; index.php (param: product_id) → product.php.

Your browser’s built-in tools let you dig into request details without leaving the window:

• Open Developer Tools (hit F12 or Ctrl+Shift+I), then switch to the Network tab.
• Go to login.php, submit your credentials. Look for the request sent (usually a POST request targeting login.php or directly redirecting to index.php). Check the Payload tab for POST parameters, or Params for GET parameters to confirm username and password.
• Repeat the process on index.php when submitting product_id: Find the corresponding request in the Network tab, check the parameter details, and verify the redirect to product.php.
• For easier later analysis, right-click the request and select Copy > Copy as cURL to save the full request including parameters and path.

Tools like Burp Suite or Wireshark let you intercept and inspect every request/response in detail:

• Using Burp Suite as an example: Configure your browser to route traffic through Burp’s proxy. Then navigate to login.php, submit your credentials—Burp will intercept the request. You’ll clearly see the target URL (login.php), the parameters (username, password), and the redirect to index.php in the response.
• When you submit product_id on index.php, Burp will catch that request too. You can examine how the parameter is passed and confirm the jump to product.php.
• These tools also let you test parameter validity (e.g., if product_id really requires a number) while building your path map.

If you can view the app’s code, this gives you the most accurate, direct view of the flow:

• Check login.php: Look for the form’s action attribute to see where credentials are submitted, and the name attributes of the input fields to confirm the parameter names (username, password). Then find the redirect logic (like header("Location: index.php")) that fires after successful login.
• Check index.php: Locate where product_id is processed (e.g., $_GET['product_id'] or $_POST['product_id']), and find the code that redirects to product.php (such as header("Location: product.php?product_id=" . $_GET['product_id'])).
• This method removes guesswork—you’ll see exactly how pages connect and parameters are passed.

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