From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=203.199.198.232; helo=imsva.in.megatrends.com; envelope-from=sivaramann@amiindia.co.in; receiver=edk2-devel@lists.01.org Received: from IMSVA.IN.MEGATRENDS.COM (Webmail.amiindia.co.in [203.199.198.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id DC3222096185E for ; Fri, 18 May 2018 02:15:24 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 575838207C for ; Fri, 18 May 2018 14:49:27 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 4ACD58207B for ; Fri, 18 May 2018 14:49:26 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS for ; Fri, 18 May 2018 14:49:26 +0530 (IST) Received: from VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5]) by Venus2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b%14]) with mapi id 14.03.0248.002; Fri, 18 May 2018 14:45:20 +0530 From: Sivaraman Nainar To: "edk2-devel@lists.01.org" Thread-Topic: reg: EDK2 - HTTP Boot Thread-Index: AdPuiJ/aBdfqyNXSTyyYd0+c1btrkw== Date: Fri, 18 May 2018 09:15:19 +0000 Message-ID: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.2.50] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.2.0.1013-23850.006 X-TM-AS-Result: No--17.514-5.0-31-10 X-imss-scan-details: No--17.514-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.2.1013-23850.006 X-TMASE-Result: 10--17.514200-10.000000 X-TMASE-MatchedRID: X8U+ZgfjRBIwfXl56Qt5SAz4VsCc1YW+g8C02zkI7w74JyR+b5tvoFla hCeVxirt+7Wbd8wpaKTp2/WQkTTCMsNOo16VCf1y+nWmWoRu6rHJ5SXtoJPLyM0NOcCuFW61+XT LmR0QQxV9DsRKD0Q+rL6Hb6RGI/VeR1vveBQPCRfBtFDYGmaWKhrL4FDGAJ+Flvs2jSyutOTsoE FnZAFTLNDbef4/mkgxZs76viGG3wHF4qvmNbXqFt/wYmMFcJSIh+w9Wz/xXDqlF7MF/8ayEjnuQ WM5Mjkl77q9ZAKNG0qURP9PtVdrmw5VocU4CFzq2x/FmlC/aoy08Z6Wwo67iLjV6s6mdtCJl1VN +kRE/iPOH38lNbOoTBQAXi4Ga9GRHxPMjOKY7A/+xOhjarOnHqYdro8t3UQW+gtHj7OwNO0XnNp rp3a9NkLdRwJpSA7HVi52ZiHkSZbnnDWLQdVg0pRs4kh0VlT8 X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0 X-Content-Filtered-By: Mailman/MimeDel 2.1.26 Subject: reg: EDK2 - HTTP Boot X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 09:15:25 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello All, There is an observation found during HTTP Boot that, when HTTP 1.1 server d= oes not support keep-alives, the system sometimes failed boot when connecti= ons are not persistent. RFC 2616 section 8.2.1 says "HTTP/1.1 servers SHOULD maintain persistent co= nnections and use TCP's flow control mechanisms to resolve temporary overlo= ads, rather than terminating connections with the expectation that clients = will retry. The latter technique can exacerbate network congestion." https://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html So the understanding here is Server should not assume or expect that client= will retry. Would like to confirm if the EDK II implementation expects the= Server should persistent connection. -Siva