Gatling Http Client Standalone

Sofiane Cherchalli

unread,

Feb 11, 2016, 4:37:39 AM2/11/16

to Gatling User Group

Hi,

I'd like to replace the spray client I'm using with in my project with async http client. Gatling provides a scala wrapper for it and much more. Would it be possible to use the gatling http client as standalone? If so, where to start from?

Thanks.

Stéphane LANDELLE

unread,

Feb 11, 2016, 5:11:24 AM2/11/16

to gat...@googlegroups.com

Hi,

I'd like to replace the spray client I'm using with in my project with async http client. Gatling provides a scala wrapper for it and much more.

Would it be possible to use the gatling http client as standalone? If so, where to start from?

No, Gatling doesn't provide a Scala wrapper on top of AHC. The Gatling DSL components are workflow step builders, that are useless outside the Gatling scope/usage.

I'm aware of 2 AHC Scala wrappers:

Dispatch, but it looks pretty stalled and really lags behind (still uses AHC 1.9.11 which is 1 year old, while AHC moves forward at fast pace).
Play WS, which is more up-to-date.

Then, IMO, except for some extra features in Play WS, like advanced certificate features, there isn't much in there you can't achieve with just bare AHC + your favorite JSON parser + an implicit for converting Java futures into Scala ones.

Stéphane Landelle

GatlingCorp CEO

slan...@gatling.io

Thanks.

--
You received this message because you are subscribed to the Google Groups "Gatling User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gatling+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Sofiane Cherchalli

unread,

Feb 11, 2016, 9:34:15 AM2/11/16

to Gatling User Group

Thanks Stéphane.

I found another wrapper: http4s

Stéphane LANDELLE

unread,

Feb 11, 2016, 10:47:46 AM2/11/16

to gat...@googlegroups.com

Fun!

They used to only support/wrap the Jetty client and Blaze-client (their own HTTP stack).

They introduced AHC support one month ago: https://github.com/http4s/http4s/commits/master/async-http-client/src

Stéphane Landelle

GatlingCorp CEO

slan...@gatling.io

--

Mayank

unread,

Jul 1, 2018, 3:07:51 PM7/1/18

to Gatling User Group

Hi Stéphane,

We are facing an issue with Gatling redirection. (Using Gatling 2.1.7)

We are loading rails server and trying to use (http://localhost:3000)

Our flow should do something like this: URL/sessions/new -> URL/session(authentication) -> Redirection to User Home -> rest of the operations.

What is happening is that after successful authentication it gets 302(redirection) to Homepage(as expected), but immediately after that is gets another 302 back to URL/sessions/new, and goes in a loop.

URL/sessions/new -> URL/session(authentication) -> Redirection to User Home -> Redirection to URL/sessions/new

Have you seen any such kind of an issue?

Regards,

Mayank