Record&Replay: regex being send in place of the actual query or header value

[rrabio]

When a response is recorded with Record&Replay, the regex values in the header and query fields are used to create the request sent to the server specified in the response.body field. The actual value should be used instead.
Example:
a request such as :
http://myserver/Search?queryvalue=ciao

intercepted by the following yaml request:

• request:
  method: GET
  url: /search
  query:
  queryvalue: "([a-zA-Z]+)"
  response:
  status: 200
  body: http://127.0.0.1:8888

will create an http request for 127.0.0.1:8888 that will contain a queryvalye=([a-zA-Z]+) rather than a queryvalue=ciao.

[rrabio]

PS. great tool Alexander and thanks for sharing it!
I'm willing to fix the bug if you agree and propose a patch, if you can give me a few pointers on where and how.
Cheers

[azagniotov]

Hi @rrabio , thanks for reporting this. I already have a fix. Will you be able to build a SNAPSHOT from the master, once I push the fix and test it on your end before I deploy it to Maven Central?

[azagniotov]

Fixed in version 4.0.4:

P.S.:
it is a little bit tricky with headers. Sending incoming request headers as-is can affect the recorded response. For now, sending only incoming request query string as-is

[rrabio]

It works perfectly now, thanks!

[azagniotov]

Releasing version 4.0.4