HTTP is a thing of beauty: a protocol that has survived longer than 20 years without changing much.
#HTTP #WebSecurity
#HTTP #WebSecurity
freeCodeCamp.org
Web Security: an introduction to HTTP
This is part 2 of a series on web security: part 1 was “Understanding The Browser”
As we’ve seen in the previous parts of this series, servers can send HTTP headers to provide the client additional metadata around the response, besides sending the content that the client requested. Clients are then allowed to specify how a particular resource should be read, cached or secured.
#HTTP #WebSecurity
#HTTP #WebSecurity
freeCodeCamp.org
Secure your web application with these HTTP headers
This is part 3 of a series on web security: part 2 was “Web Security: an introduction to HTTP”
Imagine being a backend developer who needs to implement sessions in an application: the first thing that comes to your mind is to issue a token to clients and ask them to send this token with their subsequent requests. From there onwards you are going to be able to identify clients based on the token included in their request.
#HTTP #WebSecurity
#HTTP #WebSecurity
freeCodeCamp.org
Web Security: How to Harden your HTTP cookies
Note: this is part 4 of a series on web security. Part 3 was Secure your web application with these HTTP headers.