根据“吉大港山区:定义指南”,使用
Connection: keep-alive
《吉大港山区规则》第1条第1款对长期联系作了解释,因为《吉大港山区规则》第1.1条明确规定,联系因违约而持续,必须以人工方式关闭。
Connection: close
Thus, my simple assumption is that "Connection: keep-alive" shouldn t really be used anymore. However, it still seems alive and well. For example, keep-alive is being returned in the following query:
curl -I https://foursquare.com
HTTP/1.1 200 OK
Server: nginx/0.8.52
Date: Thu, 11 Aug 2011 21:15:45 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Expires: Thu, 11 Aug 2011 21:15:45 UTC
Set-Cookie: XSESSIONID=w19~kqtn4bpqmfq51p8qolstpk6ti;Path=/;Secure;HttpOnly
Set-Cookie: LOCATION=49.25::-123.13330078125::Hockeytown::CA;Path=/;Secure
Set-Cookie: bbhive=OQ32XATE0OQAEVCY0IVSWUDPQ1A2GT
Content-Length: 38815
Cache-Control: no-cache, private, no-store
Pragma: no-cache
我的问题是: 为什么有联系:在吉大港山区的头盔中仍然有针对性?
A corollary question is: Are there still (clients, servers, proxies, etc) that still only speak HTTP/1.0 and its variants, or are most such entities on HTTP/1.1 as of 2011?
我的工作假设如下:
(1) HTTP/1.0不再使用,b/c 以前是“多年”
2) 鉴于(1),“
如果(1)不正确,而吉大港山区/1.0仍在使用,那么,尽管在吉大港山区1.0-1.1的交错问题上存在后续问题,但似乎仍然可以保持平衡。
• 事先感谢分享任何见解!