Skip to content

bug: Multiple cookie wrongly set in a single Set-Header when accessing via ELB #12633

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 task done
xtremusphone opened this issue May 17, 2025 · 6 comments
Closed
1 task done

bug: Multiple cookie wrongly set in a single Set-Header when accessing via ELB #12633

xtremusphone opened this issue May 17, 2025 · 6 comments
Assignees
@bentsku
Labels
aws:elb AWS Elastic Load Balancer status: in progress Currently being worked on type: bug Bug report

Comments

@xtremusphone
Copy link

xtremusphone commented May 17, 2025 •
edited
Loading

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

The HTTP Set-Cookie header seems to squash multiple Set-Cookie causing browser to only set the first Set-Cookie.
Image

Expected Behavior

Multiple Set-Cookie Header to be set for each of the cookie key / value pair
Image

How are you starting LocalStack?

With the localstack script

Steps To Reproduce

Access via ELB and monitor the HTTP response via network tab in the developer tool

Environment

OS: macOS Sequoia 15.4.1
LocalStack version: 4.3.1.dev89
LocalStack build date: 2025-04-30
LocalStack build git hash: 00c84d961

Anything else?

No response
@xtremusphone xtremusphone added type: bug Bug report status: triage needed Requires evaluation by maintainers labels May 17, 2025
@localstack-bot
Copy link
Collaborator

Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Support if you are a licensed user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines.

@bentsku
Copy link
Contributor

bentsku commented May 19, 2025 •
edited
Loading

Hello @xtremusphone and thanks for your report!

Could please confirm from what type of target you are getting the response of in this case? Is it a target for a container?
Thanks!

Note: similar to already solved API Gateway issue #12577

@bentsku bentsku added aws:elb AWS Elastic Load Balancer status: backlog Triaged but not yet being worked on and removed status: triage needed Requires evaluation by maintainers labels May 19, 2025
@bentsku bentsku self-assigned this May 19, 2025
@bentsku bentsku added status: in progress Currently being worked on and removed status: backlog Triaged but not yet being worked on labels May 19, 2025
@xtremusphone
Copy link
Author

Hi bentsku,

Yeap the target is an ECS instance (the second screenshot is direct call to the ECS instance)

@bentsku
Copy link
Contributor

bentsku commented May 22, 2025

@xtremusphone thanks for the response! I have a fix in the works, it's probably going to be merged next week, sorry for the delay on that one. I'll update you once it is available in the latest Pro image.

@bentsku
Copy link
Contributor

bentsku commented May 26, 2025

Hello @xtremusphone! The latest image should now contain the fix for your issue. Could you try running docker pull localstack/localstack-pro:latest, and give it a try with that image to see if that solves your issue?

Thank you!

@xtremusphone
Copy link
Author

Hi @bentsku ,

Seems the issue has been resolved. Thanks for the quick response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bentsku bentsku

Labels
aws:elb AWS Elastic Load Balancer status: in progress Currently being worked on type: bug Bug report
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xtremusphone @bentsku @localstack-bot