Hi,
This is related to my other 'cookie' post - but that other post has side tracked onto another issue I need to solve - so I've created a second post with a specific issue.
A while back @nmrao created the script assertion below to extract the 'Set-Cookie' http header values and write them to corresponding 'Cookie' http headers, so if 4 'Set-Cookie' headers are included on the initial request, 4 'Cookie' headers with the relevant values (including all the additional header value attributes) are added to the nextStep.
//Courtesy of Rao
//This script assetion reads the http response,
//collect the cookies for the next http request
//Provide the next step name where you want to set the Cookie to the request or
//Use property expansion for below
def nextStepName = 'REST Request'
def nextRequest = context.testCase.testSteps[nextStepName].httpRequest
def headers = nextRequest.requestHeaders
if (messageExchange.responseHeaders.containsKey('Set-Cookie')) {
log.info "Found Cookie in the response headers"
def cookiez = messageExchange.responseHeaders['Set-Cookie'].value
def list = []
cookiez.each { cookies ->
//def (name, value) = cookies.toString().split('=',2)
list.add(cookies.toString())
}
headers['Cookie'] = list
} else {
log.warn "Not Found Cookie in the response headers"
}
nextRequest.requestHeaders =
The above is great - exactly what I was told I needed - however, what the developers have now told me is that what I need is slighlty different from the above - despite them saying the above gave me what I need! aah! frustrating!
The http Set-Cookie/Cookie theory (according to the following links (link1 and link2) indicates that the 'Set-Cookie' header values (without the additional attributes) are used to populate the follow up single Cookie header value.
so if we receive in the initial message
Set-Cookie: returnurl=345678; Max-Age=3600; Expires=Tue, 18-Jun-2019 22:58:30 GMT; Path=/; Secure; HttpOnly
Set-Cookie: authtype=234567; Max-Age=3600; Expires=Tue, 18-Jun-2019 22:58:30 GMT; Path=/; Secure; HttpOnly
Set-Cookie: state=123456; Max-Age=3600; Expires=Tue, 18-Jun-2019 22:58:30 GMT; Path=/; Secure; HttpOnly
Set-Cookie: nonce=456789; Max-Age=3600; Expires=Tue, 18-Jun-2019 22:58:30 GMT; Path=/; Secure; HttpOnly
The follow up request would have ONE individual 'Cookie' http header and the value would be made up of the semi colon delimited Set-Cookie values without the additional attributes - so the follow up message's 'Cookie' header would appear as follows:
Cookie: returnurl=345678; authtype=234567; state=123456; nonce=456789
Apparently what I've described above is standard http Set-Cookie/Cookie handling and I was told I should've known about this already!
I'm stuck updating the script.
Essentially I need to concatenate all the Set-Cookie header VALUES into a single string (semi colon delimiter for each value) - but strip out the additional attributes like Max-Age, Expires, http, secure etc.
Can anyone help out? I know I'm asking a lot here - especially when everyone's already helped so much already
I need to pass the 4 'Set-Cookie' header values into the 1 'Cookie' value (stripping out all the attributes so the only the Set Cookie header values are included - apparently this is supposed to be how http 'Set-Cookie' and http 'Cookie' headers work. The server sends the Set-Cookie headers to tell the client to send a single Cookie http header and the value populating the Cookie are.
Thanks guys - really!
richie
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
SmartBear.com
Academy
Resources
License Portal
Store
Support
