Whatever "problems" are. 'sameSite' applies certain restrictions when to deliver cookies. Without it, you might expose cookies to sites that don't need it (as I understand). So there might be a privacy concern. You have to read more about sameSite if this matters to you.
Regards, Tim On 16.02.20 14:05, Peng Yu wrote: > Could the lack of sameSite cause some problems when using wget to access > certain website? Thanks. > > On Sun, Feb 16, 2020 at 4:54 AM Tim Rühsen <[email protected] > <mailto:[email protected]>> wrote: > > A conversion tool would be nice, indeed. > > Most of the fields are the same. 'hostOnly' is represented in > wget/netscape cookies.txt by NOT having a leading dot for the domain. > E.g. '.example.com <http://example.com>' means NOT hostOnly (= > cookie is valid also for all > subdomains). > > Our cookie format does not have 'sameSite' and there is no 'storeId'. > > Everything else should be mapped 1-1. > > Regards, Tim > > > On 16.02.20 02:03, Peng Yu wrote: > > Hi, > > > > > > https://apple.stackexchange.com/questions/232433/where-are-google-chrome-cookies-stored-on-a-mac > > "Session cookies are only stored in memory, but the rest are in > > ~/Library/Application Support/Google/Chrome/Default/Cookies, it's an > > sqlite3 database." > > > > I see that session cookies are not stored in a file. So there is no > > way to let wget work with google chrome cookies since session cookies > > are not available? > > > > Also, the cookie fields of google chrome is not exactly the same as > > netscape cookies format used by wget. How are the fields mapped to > > each other? Thanks. > > > > https://developer.chrome.com/extensions/cookies > > http://www.cookiecentral.com/faq/#3.5 > > > > -- > Regards, > Peng
signature.asc
Description: OpenPGP digital signature
