Neoload录制UI脚本报错：页面未重定向，返回200而非301

Hey there, let's work through this redirect issue you're hitting when recording UI scripts in Neoload. Getting a 200 status instead of the expected 301 can be frustrating, but let's break down the most common causes and fixes step by step:

1. Check Neoload's Redirect Recording Settings #

Neoload’s default configuration might be auto-following redirects, which means it skips recording the 301 response and jumps straight to the final 200 page. Here’s how to adjust it:

• Open your project’s Recording Settings
• Navigate to HTTP > Advanced Recording Options
• Look for the "Follow redirects" or "Record redirect steps" toggle. Disable auto-follow if it’s enabled, so Neoload captures the full redirect chain including the 301 response.

2. Eliminate Browser Cache Interference #

Browsers often cache redirect responses, which can cause Neoload to record a direct 200 instead of the 301. Fix this by:

• Clearing your browser’s cache, cookies, and local storage before starting the recording
• Or, launch the recording using your browser’s incognito/private mode—this ensures no cached redirects skew the results.

3. Verify if the Redirect is Client-Side (JavaScript/Meta Tag) #

Sometimes redirects happen on the client side instead of via an HTTP 301. Examples include:

• A <meta http-equiv="refresh" content="0; url=https://example.com"> tag in the page source
• JavaScript like window.location.href = "https://example.com"

Neoload’s HTTP-level recording won’t pick up these client-side jumps. To fix this:

• Switch to Neoload’s UI-based recording (instead of HTTP recording) to capture browser-level navigation
• Or, manually add a redirect step in your script after the 200 response, mimicking the client-side logic you find in the page code.

4. Validate Neoload Proxy Configuration #

Neoload acts as a proxy during recording, and misconfigured proxy settings can alter or drop redirect headers. To check:

• Go to Recording Settings > Proxy
• Ensure no options like "Modify HTTP headers" are enabled that might interfere with response codes
• Use a tool like curl or Wireshark to send the same request outside Neoload. If the server returns a 301 here but not in Neoload, the proxy configuration is likely the culprit.

5. Confirm Server-Side Behavior #

It’s possible the server is returning a 200 under specific conditions (e.g., your test user has a cookie that bypasses the redirect, or the User-Agent string differs). Test this by:

• Using curl with the exact same headers (User-Agent, Cookies, etc.) that Neoload sends during recording:

  curl -v https://your-target-url.com --user-agent "Neoload-Recorder/7.0" --cookie "your-cookie-here"
  

• If curl also returns a 200, you’ll need to investigate the server’s redirect logic (e.g., check if the redirect is only triggered for first-time visitors or specific user states).

Try these steps in order—start with the simplest fixes like clearing cache and checking settings before moving to deeper debugging. If you can share snippets of the request/response headers from Neoload’s recorder, that’ll help narrow things down even more!

内容的提问来源于stack exchange，提问作者Dheeraj A S