Gatling and Chrome response mismatches

Hi All,

I’m testing a proprietary web application and I’ve hit a road block with it. I’m able to access the login page and POST the credentials. However, when I execute requests for the next page, I see that the application is logging me out. I found that this is because the POST for submitting credentials result in a redirect with a new session id in chrome, and Gatling always records a 200 with old session id. Not sure if I’m doing something wrong with the recording or with the parameters.

Below are the http parameters.

.disableResponseChunksDiscarding //(Tried with and without this option)
.acceptEncodingHeader(“gzip, deflate”)
.userAgentHeader(“Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36”)


Please ignore this - It was a hidden field and the value was hard coded by recorder.