The QRZ server sets a transient, or temporary, cookie when a user first logs in to the site. This cookie is destroyed when the user ends the current browser session or when the user logs out of the QRZ site. When a user first logs in to the QRZ site, either via the Logon or MyQRZ pages, a session cookie is established and stored on the server. When the user attempts to access another QRZ resource, e.g., another application such as the callsign information update editor, the resource can use the session cookie that is set in the browser to verify the identify of the user without requiring that an additional password be used. Reality Much has been written regarding the security risks associated with cookies.
Cookies can damage a system or the files on that system.
A cookie is a short piece of data, not executable code. It can not do anything to the client system. A cookie is a short piece of data, not executable code. It can not do anything to the client system. A cookie can only include information that is contained in the cookie and that which was originally sent to the browser by the issuing server.