No longer see response body when TRACE enabled

When creating/debugging scripts I typically enable request/response logging in the logback.xml and redirect the logs to a file.

I recently tried the same with 3.0 and noticed that the response body is not logged.

I’m adding the following logger statement…

Am I missing something? Is there a workaround?

Thanks in advance…

–Chris

I just checked with the 3.0.0 bundle from maven central and it works just fine:

21:33:37.710 [TRACE] i.g.h.e.r.DefaultStatsProcessor -

Request:
request_1: OK

Session:
Session(Scenario Name,1,1542054817505,Map(gatling.http.ssl.sslContexts → SslContexts(io.netty.handler.ssl.OpenSslClientContext@5b08aae6,None), gatling.http.cache.dns → io.gatling.http.cache.DnsCacheSupport$$anon$1@4998a90f, gatling.http.cache.baseUrl → http://computer-database.gatling.io),0,OK,List(),io.gatling.core.protocol.ProtocolComponentsRegistry$$Lambda$434/1509713998@4ef12688)

HTTP request:
GET http://computer-database.gatling.io/
headers=
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8
DNT: 1
Accept-Language: en-US,en;q=0.5
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20100101 Firefox/16.0
Referer: http://computer-database.gatling.io/
accept-encoding: gzip, deflate
origin: http://computer-database.gatling.io
host: computer-database.gatling.io

HTTP response:
status=
303 See Other
headers=
Server: nginx/1.12.1
Date: Mon, 12 Nov 2018 20:33:37 GMT
Content-Length: 0
Connection: keep-alive
Keep-Alive: timeout=5
Location: /computers

So I suspect this is an issue on your side (not properly saving the log conf, not rebuilding project)

Regards,