Leapp Multi-Console Causes 400 Request Header or Cookie Too Large on Amazon.com
Closed this issue · 6 comments
Describe the bug
After using the Leapp multi-console for some period of time, there is an accumulation of cookies that begin with ##LEAPP. When visiting the amazon retail site (amazon.com), I get the following error:
400 Bad Request
Request Header Or Cookie Too Large
If I remove these ##LEAPP## cookies, I can browse the site again normally. After using the multi-console again for some time, I again get the same error.
Leapp Version
Version 0.22.1 (0.22.1)
To Reproduce
Steps to reproduce the behavior:
- Use leapp multi-console for a period of time until you have a lot of cookies
- Browse to https://amazon.com
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Desktop (please complete the following information):
- OS: MacOS
- OS Version: Sonoma 14.1.1 (23B81)
- Leapp Version: Version 0.22.1 (0.22.1)
As a possible quick-fix solution, could you scope the cookies to console.aws.amazon.com rather than .amazon.com?
Has anyone looked at this? It's occurring daily for me now.
We are actively looking into that right now, I'll get back to you
@mcalhoun this issue should have been fixed with the latest v0.1.8 Web Extension release. We're going to close it as soon as you confirm it's working as expected.
It seems to have been resolved for me. I'll definitely let you know if it shows up again. Thanks!