3 ms·
A HTTP response may ask the user agent to keep a cookie. The user agent is free to do so, reject it, or ask the user (as Konqueror did). It is not the respons
by jeofken 6y ago
A HTTP response may ask the user agent to keep a cookie.
The user agent is free to do so, reject it, or ask the user (as Konqueror did).
It is not the responsibility of everyone responding to HTTP requests to ask to ask “I ask you if I can ask you to keep this cookie”.
Remembering that HTTP is a format of messages being sent between people, it’s clear to me that this law is unwise. Likely written by Eurocrats who don’t understand HTTP.
- rafram 6y agoIn principle, yes, but if a browser asks a non-technical user whether they want to accept a cookie called "__Secure-3PAPISID" (an actual Google tracking cookie) with gibberish contents, what are they supposed to say? How can they understand what that means?
- jeofken 6y agoIt’s true that those who don’t understand what a HTTP cookie is, are unable to make informed decisions about them. Forcing those who reply to HTTP messages to ask if they can send a header asking if they can save a cookie does not change that - the user who clicks the cookie popup may still now understand what they do. Many do understand things like private mode though, which is nice.