seanmonstar
Refactor cookie store handling into a middleware
There's some code duplication for storing cookies internally, it would be good to clean it up into a single place as a service middleware that both the hyper client and the h3 client can share.
I noticed that a h3 client takes a cookie_store when calling new(),default async client creates a Jar as a cookie_store,do you mean extracting those lines to a function or adding a completely new struct to perform both "store" and "manage" for all cookies from all urls? @seanmonstar
I noticed that a h3 client takes a cookie_store when calling new(),default async client creates a Jar as a cookie_store,do you mean extracting those lines to a function or adding a completely new struct to perform both "store" and "manage" for all cookies from all urls? @seanmonstar
my solution to the latter #2701
can i work on this??
Hmm, I had some ideas to address this, thanks you @Lori-Shu @0x676e67 for your previous work.
