Cookie handling
Open
Nobody has claimed this yet.
Estimation - 5 (L)
Login
sdk-involved
- Dominant language
- Swift
- Stars
- 251
- Forks
- 142
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 3
Description
Server side works in a session-oriented way. When the authentication process successes, some cookies are returned inside the response headers with the key Set-Cookie.
Currently, iOS app is not handling cookies, so every request is creating a new session per user, flooding the session list:
Cookies sent by the server must be used in the following requests
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by tracing the iOS authentication response handling and the construction of subsequent requests, then verify that server Set-Cookie headers are retained and sent on later requests so one user session is reused instead of creating a new session each time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100