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
Internal server error when sending duplicate cookie #567
Comments
Yeah, poor modelling decision on my part. Cookies are represented by a map internally and the map builder blows up if you try to add more than one with the same key. I'll switch to a list when I get the chance. |
Thanks. If you need help I can try to make a PR, but I need some guidance first given that I'm not familiar with the code. |
If you fancy having a go at it, it's primarily about changing |
Ok, I'll take a look on those and try to open a PR. |
Hi, I'm facing the same problem. Can you suggest any workarround for this issue without changing the version of wiremock? Thanks in advance! |
Hi @mmodenesi I solved the problem by removing the duplicated cookies in my front end app. Unfortunately I failed to submit a PR to fix this, I'll try again when I have a free time |
Thank you. Going that way I found that the issue was related to Firefox 46.0 sending duplicate cookies, not my application. Upgrading the browser solved the issue. |
Fixed in 827e7cc |
Hi.
I'm experiencing a strange error in wiremock.
Let's say I have the following mapping:
If I make a request with two values for one cookie, like this:
I get the following response:
But if I remove the duplication, it works. For example:
I know that we shouldn't set the cookie value twice, but in my real life case I really can't control that.
What could I do?
Also, I've tried to debug wiremock but I didn't go too far. Is there any debug flag (I'm already using --verbose) that I can see the stacktrace?
The text was updated successfully, but these errors were encountered: