Content deleted Content added
Pleasancoder (talk | contribs) m →Secure and HttpOnly: minor clarification |
Pleasancoder (talk | contribs) m →Network eavesdropping: use new RFC reference |
||
Line 256:
An attacker could use intercepted cookies to impersonate a user and perform a malicious task, such as transferring money out of the victim’s bank account.
This issue can be resolved by securing the communication between the user's computer and the server by employing [[Transport Layer Security]] ([[HTTPS]] protocol) to encrypt the connection. A server can specify the ''Secure'' flag while setting a cookie, which will cause the browser to send the cookie only over an encrypted channel, such as an SSL connection.<ref
=== Publishing false sub-___domain – DNS cache poisoning ===
| |||