Onè

I rebased the PR and made a few lint related commits. I reviewed the code again in light of https://github.com/seanmonstar/reqwest/pull/1449 and they are very similar. I put a lot more...

PS. Maybe somewhere we should add a warning that WASM cookies won't work for WebSockets because according to https://devcenter.heroku.com/articles/websocket-security#authentication-authorization > Since you **cannot customize WebSocket headers from JavaScript**, you’re limited...

I think the current version PR as is still be helpful for more than just me.and the Websocket issue is kinda out of reach without trying to use the browsers...

> @c-git i'd recommend reaching out to sean on the #reqwest channel in the tokio discord to discuss a review directly - https://discord.gg/PWCbbMcy > > cc @seanmonstar as well Thank...

> Thanks for working on this! I've wondered a bit, since reqwest on wasm is backed by fetch, can we really manage cookies separately? I don't think we have a...

Thank you, for that information. I'll try to replicate what you did and then try my code again without cookie support in WASM and see what happens with the cookies...

Got tied up with other tasks and haven't been able to finish more detailed testing yet but it does seem that the browser does automatically manage the cookies (Sorry I'd...

I setup a small test server and cookies are set, unset and sent but they are done by the browser. There is no cookie information in the incoming requests that...

@GsnMithra Have you seen the code from this discussion https://github.com/Byron/google-apis-rs/discussions/345#discussioncomment-6865376 ? The OP said it worked for them.

Ok I understand. I'm sorry to hear that though as that's what I use on Ubuntu. If I'm able to manage the time and can replace it with the new...