Learning Revisited

Wednesday, May 6, 2015

Why we need keep-alive header in HTTP response

An typical keep-alive response looks like this:

Keep-Alive: timeout=15, max=100

More: http://stackoverflow.com/questions/20592698/keep-alive-header-clarification
Posted by Learner at 3:27 PM
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Labels: handshaking, http, IP, keep-alive, port, TCP

No comments:

Post a Comment

Newer Post Older Post Home
Subscribe to: Post Comments (Atom)

Labels

algorithms data structures java

Blog Archive

  • ▼  2015 (18)
    • ►  June (1)
    • ▼  May (10)
      • Quick Squid proxy installation on Cent OS
      • Some useful Redis commands - quick view
      • Memcached vs. Redis
      • Redis Quick installation on CentOS
      • Difference between REST Services and Restless SOAP...
      • OAuth 2.0: Why we need it, What are the benefits a...
      • Design Patters in Java core library
      • How does load balancer actually work
      • Servlets vs thread safety
      • Why we need keep-alive header in HTTP response
    • ►  April (7)

About Me

Learner
View my complete profile

Send a note to Blogger

Name

Email *

Message *

Awesome Inc. theme. Powered by Blogger.