Elaborate on non-design goal of parsing set-cookie

Open
#8 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
api, backend

Research direction

Start by reading Biscotti's existing response-header handling and the stated non-goal around parsing Set-Cookie. Clarify the intended parsing scope and validation behavior before implementation; done means the agreed Set-Cookie response headers parse correctly without changing existing cookie-management behavior.

Written by the indexing model from the issue text.

Description

Biscotti looks great and I love the direction you took way this crate from the 'cookie' crate.

I wonder however why parsing Set-Cookie headers is such a non goal? Feels like you already have everything in place for response headers, only the parsing is missing.

In case it is due to time constraints, I could offer to contribute this for you. Otherwise I might need to fork it for my own purposes if you don't mind as I do really need that support.

Either way, thanks for your blog and crate, it's a nice refreshing take on cookies.

Dominant language
Rust
Stars
125
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LukeMathWalker/biscotti

All issues in LukeMathWalker/biscotti

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.