gatling.http.referer issue with request context

I have a simulation that is resulting in a 404 due to the “gatling.http.referer” adding an extra context to the request. Here is a TRACE. Notice the “am/am” in the Session object. The “referer” in the HTTP headers is ok. Is this a bug or do i need to clear the session after each request in the feeder?

Note that previously the exact same simulation works with version 3.1.2. Some irrelevant data has been removed below to make it terse.

00:26:36.884 [DEBUG] i.g.h.e.r.DefaultStatsProcessor - Request ‘Get SAML response’ failed for user 1:, but actually found 404
00:26:36.885 [TRACE] i.g.h.e.r.DefaultStatsProcessor -

Get SAML response: KO, but actually found 404

Which version are you trying to upgrade to ?
Please provide logs with the Set-Cookie response header.

Please provide the full logs, including previous requests.


typescript.404.public.txt (30.2 KB)

I must point out that the previously attahed full log trace is actually from 3.3.1 but i experience the exact same issue with 3.6.0. I can provide the 3.6.0 logs if need be.

So this am/am in the url and referer is already there in 3.3.1. Looks like a bug in your code.

I suspect you’re hacking the “gatling.http.referer” attribute yourself and are overriding the value Gatling sets.

Entirely possible that there is a bug in my code. But this code works with 3.1.2. Let me try and get the TRACE from 3.1.2.

So i inherited the code but as far as i can tell this attribute is not being tinkered with. I will double check tough.

Sorry, but I won’t have time to try to spot the difference between your different versions.
Please investigate yourself and let me know once you’ve spotted something.