Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only the last Set-Cookie header in response is being preserved. #137

Closed
distributedlife opened this issue Apr 20, 2016 · 0 comments
Closed
Milestone

Comments

@distributedlife
Copy link
Contributor

I'm experiencing a situation where only the last set-cookie response header is being stored by mountebank. I'd love some advice on what to do in this situation. Happy to fork/PR if I know where to look.

If I curl the running webserver I get the following:

❯ curl -ik https://www.website.com/ws-api/v1/client/session
HTTP/1.1 200 OK
Server: nginx
Content-Type: application/json;charset=UTF-8
Content-Length: 115
Date: Wed, 20 Apr 2016 01:18:14 GMT
Connection: keep-alive
Set-Cookie: JSESSIONID=86752943865765SDSDFSD.APP4P; Path=/; Secure; HttpOnly
Set-Cookie: JSESSIONID=86752943865765SDSDFSD.APP4P; Path=/; HttpOnly
Set-Cookie: herpderp=1461115394~id=485273495872645634re23467; path=/

If I curl via mountebank I get the following

❯ curl -ik https://localhost:9002/ws-api/v1/client/session
HTTP/1.1 200 OK
Server: nginx
Content-Type: application/json;charset=UTF-8
Content-Length: 115
Date: Wed, 20 Apr 2016 01:18:18 GMT
Connection: close
Set-Cookie: herpderp=1461115394~id=485273495872645634re23467; path=/
Access-Control-Allow-Origin: https://localhost:8010
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants