Follow an overview of methods like TCP FastOpen, TLSv1.3, 0-RTT, and HTTP/3 to reduce handshake delays and improve server response times in secure environments.
Some of the techniques that could be used to defend from replay attacks are:
* limiting the HTTP-types of the request allowed: GET, HEAD and OPTIONS only;
* limiting a time frame and total requests size before a new handshake will be required;
* HTTP-headers as they are encrypted could also be used to add unique identifiers to the requests.
Interesting point about balancing between monolithic and microservices architectures as a project scales. How do you decide when to make that shift, especially if the team is small and resources are limited?
Comments
Dec 04, 2024 · Maksim Kupriianov
Some of the techniques that could be used to defend from replay attacks are:
* limiting the HTTP-types of the request allowed: GET, HEAD and OPTIONS only;
* limiting a time frame and total requests size before a new handshake will be required;
* HTTP-headers as they are encrypted could also be used to add unique identifiers to the requests.
Dec 02, 2024 · Maksim Kupriianov
Thanks Bruce! Fixed
Nov 11, 2024 · Maksim Kupriianov
hahah thanks for your kind words
Nov 11, 2024 · Grigorii Novikov
Interesting point about balancing between monolithic and microservices architectures as a project scales. How do you decide when to make that shift, especially if the team is small and resources are limited?