You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We test the PKCE oauth flow with XLT and we have to extract parameters from the 'location' header of a response.
Currently we use the workaround: store response header value for 'location' into variable, when using the variable transform the value via beanshell call to custom extraction method.
It would be more elegant to directly extract the needed value into the variable when receiving the header response.
Perhaps something like this:
- Action :
...
Response :
Store :
- code :
Header : location
Regex : "code=([a-z0-9A-Z]*)"
Group : 1
The text was updated successfully, but these errors were encountered:
- added regex support to Header and Cookie extractors
- added corresponding unit tests
- adjusted the cheat sheet with examples
- updated dependencies
- prepared beta release
…er (#19)
- added regex support to Header and Cookie extractors
- added corresponding unit tests
- adjusted the cheat sheet with examples
- updated dependencies
- prepared beta release
Co-authored-by: Joerg Werner <j.werner@xceptance.de>
We test the PKCE oauth flow with XLT and we have to extract parameters from the 'location' header of a response.
Currently we use the workaround: store response header value for 'location' into variable, when using the variable transform the value via beanshell call to custom extraction method.
It would be more elegant to directly extract the needed value into the variable when receiving the header response.
Perhaps something like this:
The text was updated successfully, but these errors were encountered: