JMeter URL redirection challenges from 302 to 200 status code

[mshemadarshini]

I'm trying to perform URL HTTP connection authentication with JMETER and facing challenges on redirection URL with JMeter from 302 to 200 status code within the organization environment. The office environment using windows authentication NTLM2 methods.

However I’m facing URL redirection blockage when I tried to navigate through an internal website as it stops when it reaches 302 status code and failed to navigate further to status code 200 through JMeter but when I display the same URL with chrome browser, it able to successfully display the web with status code 200 using chrome browser.

How does the URL Authentication work?

1. at 1st the given URL which includes end-user parameters were entered to display the web messages.[shows HTTP status code 302]
2. The URL then redirects to another portal login URL to acknowledge the authentication.[shows HTTP status code 302]

Problem/Issue:-

• The URL only successfully performing the 1st 2 options but it failed to perform the final redirection to have status code 200
• At the moment the HTTP result in Jmeter through "View Result Tree" and "View Result Table" is both showing status code 302

Limitation

• I couldnt install any external chrome pluggin due to the security restriction within the given operating system environment
• proxy has been included. in both "HTTP default Advance" option and "HTTP Advance" option with the relavent user proxy details, id and password

Additional Details

• The website were build part of the liferay framework using java spring.
  • We notice through jmeter logs viewer that the "Pooling HTTP Connection Manager" being shut down as well.
  • I've included the log viewer from the JMETER in here

Challenges

• Kindly advise on the further configuration on this.

[jagan996]

Did you get resolution for the reported issue. We are also have similar issue now

[rsneha027]

Check if the server is using Keep-Alive connections. If so, make sure JMeter is also using Keep-Alive by setting the httpclient4.parameters property in jmeter.properties to http.connection.stalecheck$Boolean=true.

Inspect the response data in the View Results Tree to see if there are any clues about the issue. Look for any error messages or other useful information that might help you identify the problem.

Also check if the redirection path in the HTTP response is absolute or relative. You can use this tool redirect checker to get it’s detail redirection path and its status code.

Sometimes, applications may use relative URLs for redirection. If the redirection path is relative, make sure it is resolved correctly by the client (JMeter) to access the correct URL.