I’ve encountered a problem with Gatling’s get-function. This problem relates to the Durandal Router and the way the URL’s are getting built.
Take this script:
val scn = scenario(“test”)
Gatling will request www.google.com and not the full url. Have anyone encountered this before? Any clues to a workaround?
Any help to solve this would be greatly appriciated!
Thanks for the quick reply.
I understand what you’re saying and what the generic syntax says about fragments, but that’s not the case in this situation. Due to Durandal Router, the # is a part of the URI that has to be sent to the server.
Is there anyway to make Gatling send the information to the server?
torsdag 13. august 2015 14.16.39 UTC+2 skrev Stéphane Landelle følgende:
Do you have an online Durandal or Aurelia sample that would exhibit how a browser would send such fragment?
I’m afraid not, this is a part of a log in process and the only version available online, is the live system.
This is an example of what the request URL looks like from a browser:
Exactly how this works server side, I don’t know. I’m just in charge of performance testing and haven’t been a part of the development process.
Honestly, I really doubt the fragment is sent to the server over the wire. Plus Durandal is only a front end framework and has nothing to do with what happens on the server side.
So without an example that proves me wrong, there’s nothing I can do.