3 ms·
To be clear, cookies are an HTTP header field that can carry any text data you want. You can pass plain text, JWTs or any other encrypted payload (which many we
by manigandham 8y ago
To be clear, cookies are an HTTP header field that can carry any text data you want. You can pass plain text, JWTs or any other encrypted payload (which many web frameworks do automatically).
JWTs aren't comparable to cookies, they're just a standard way to sign data.
- pkulak 8y agoHis or her point was that if you don't sign and/or encrypt, there's no benefit over a standard cookie.
- techslave 8y agonot sure if that was the point or not, but it's wrong. even if you did sign/encrypt, that's not a benefit over a standard cookie. you can easily sign or encrypt a 'standard cookie' as well. the benefit is the portability that comes from a standardized and widely used data structure.
- kbenson 8y agoYou say that as if cookies haven't been a standardized and widely used data structure (key-value store) for decades.
- johncolanduoni 8y agoNo, they say it as if cookies don’t have a built in authentication or encryption method (when the client is untrusted).
- KaiserPro 8y agoMy point was that allowing 'None' was/is a flaw. If you want to shuttle bits of data about in an unsigned/unencrypted/insecure way, that's what raw cookies are for. Now, as cookies are buckets to dump data, there is of course nothing to stop you encrypting, signing and doing all sorts of things to cookies.