aws / aws/serverless-java-container

Problems Reading Cookies

Open
#274 4 comments 0 reactions 0 assignees View on GitHub
need feedback
Dominant language
Java
Stars
1.6k
Forks
574
PR merge metrics
No merged PRs in 30d

Description

* Framework version: 1.3.2
* Implementations: Spark

## Scenario
Lambda is fronted by API Gateway which is in turn fronted by cloudfront which is the host of the public vanity URL.

Code is the lambda is looking for a cookie but cannot get get. I assume that this is because it's not getting x-forwarded data? In a similar situation with a ELB running Spring/tomcat we had a similar problem and needed to add the following properties to Spring:

server.tomcat.remote-ip-header=x-forwarded-for
server.tomcat.protocol-header=x-forwarded-proto

I assume there is something like this for Spark? I don't see anything in their documentation?

## Expected behavior
Can read cookies on the vanity domain

## Actual behavior
no cookies :(

## Steps to reproduce
Create the above scenario

Thank You!

Contributor guide

Open the contributing guide

Research direction

Start by tracing how cookies are exposed to the Java Spark implementation when requests pass through API Gateway and CloudFront. Compare the reported vanity-domain scenario with the existing serverless-java-container documentation and request handling behavior; done means cookies can be read in that deployment path.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, java
Domain
api, backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.