HTTP: Make header Methods Accept CharSequences as Values

Gatling 3.4 deprecates io.gatling.http.HeaderValues in favour of io.netty.handler.codec.http.HttpHeaderValues. Hence, all header value constants are now AsciiStrings, not Strings. However, the various methods for setting headers still demand Strings as values. They should be changed to accept CharSequences (or Expression[CharSequence]s) as values instead.

In a nutshell, I want to be able to write:

http("example")
    .get("/my/url")
    .header(ACCEPT, TEXT_HTML)
    .headers(Map(    
        CACHE_CONTROL → NO_CACHE,
        PRAGMA → NO_CACHE
    ))

currently, I am forced to write:

http("example")
   .get("/my/url")
   .header(ACCEPT, s"$TEXT_HTML")
   .headers(Map(    
       CACHE_CONTROL → s"$NO_CACHE",
       PRAGMA → s"$NO_CACHE"
   ))

[slandelle]

Thanks for reporting.

We’ll have to weight going this way or revert the deprecation. If we could the former, I’m afraid this is not something we’ll be able to do before Gatling 3.5.0 because it would break binary compatibility.

[jGleitz]

#3973 is also a good solution for us. Thank you for addressing the issue!