<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Remote Attestation Process - problem with IAS response in Intel Confidential Computing</title>
    <link>https://community.intel.com/t5/Intel-Confidential-Computing/Remote-Attestation-Process-problem-with-IAS-response/m-p/1171303#M3214</link>
    <description>&lt;DIV class="field field-name-body field-type-text-with-summary field-label-hidden"&gt;
	&lt;DIV class="field-items"&gt;
		&lt;DIV class="field-item even"&gt;
			&lt;P&gt;Hello.&lt;/P&gt;

			&lt;P&gt;I did the process of remote attestation in a NodeJS application. When I tried to do a post to IAS, with the main NodeJS modules for request, I received this error:&lt;/P&gt;

			&lt;P&gt;error: { Error: Parse Error&lt;BR /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSSocket.socketOnData (_http_client.js:411:20)&lt;BR /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at emitOne (events.js:96:13)&lt;BR /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSSocket.emit (events.js:191:7)&lt;BR /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at readableAddChunk (_stream_readable.js:178:18)&lt;BR /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSSocket.Readable.push (_stream_readable.js:136:10)&lt;BR /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSWrap.onread (net.js:559:20) bytesParsed: 195, code: 'HPE_UNEXPECTED_CONTENT_LENGTH' }&lt;BR /&gt;
				&amp;nbsp;&lt;/P&gt;

			&lt;P&gt;Searching about this problem, I found out that this is related to a malformed response from IAS, as stated in:&lt;BR /&gt;
				-&lt;A href="http://stackoverflow.com/questions/35525715/http-get-parse-error-code-hpe-unexpected-content-length" rel="nofollow"&gt;http://stackoverflow.com/questions/35525715/http-get-parse-error-code-hpe-unexpected-content-length&lt;/A&gt;&lt;/P&gt;

			&lt;P&gt;-&lt;A href="https://github.com/nodejs/node/issues/5754" rel="nofollow"&gt;https://github.com/nodejs/node/issues/5754&lt;/A&gt;&lt;/P&gt;

			&lt;P&gt;-&lt;A href="https://github.com/nodejs/node/issues/6517" rel="nofollow"&gt;https://github.com/nodejs/node/issues/6517&lt;/A&gt;&lt;BR /&gt;
				&amp;nbsp;&lt;/P&gt;

			&lt;P&gt;As a workaround, I had to use a module based on curl. Can anyone please explain me if this format of the response from IAS could be "fixed" and avoid future problems with other developers?&lt;/P&gt;

			&lt;P&gt;Thank you.&lt;/P&gt;
		&lt;/DIV&gt;
	&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Tue, 22 Aug 2017 19:23:22 GMT</pubDate>
    <dc:creator>Dalton_V_</dc:creator>
    <dc:date>2017-08-22T19:23:22Z</dc:date>
    <item>
      <title>Remote Attestation Process - problem with IAS response</title>
      <link>https://community.intel.com/t5/Intel-Confidential-Computing/Remote-Attestation-Process-problem-with-IAS-response/m-p/1171303#M3214</link>
      <description>&lt;DIV class="field field-name-body field-type-text-with-summary field-label-hidden"&gt;
	&lt;DIV class="field-items"&gt;
		&lt;DIV class="field-item even"&gt;
			&lt;P&gt;Hello.&lt;/P&gt;

			&lt;P&gt;I did the process of remote attestation in a NodeJS application. When I tried to do a post to IAS, with the main NodeJS modules for request, I received this error:&lt;/P&gt;

			&lt;P&gt;error: { Error: Parse Error&lt;BR /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSSocket.socketOnData (_http_client.js:411:20)&lt;BR /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at emitOne (events.js:96:13)&lt;BR /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSSocket.emit (events.js:191:7)&lt;BR /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at readableAddChunk (_stream_readable.js:178:18)&lt;BR /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSSocket.Readable.push (_stream_readable.js:136:10)&lt;BR /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSWrap.onread (net.js:559:20) bytesParsed: 195, code: 'HPE_UNEXPECTED_CONTENT_LENGTH' }&lt;BR /&gt;
				&amp;nbsp;&lt;/P&gt;

			&lt;P&gt;Searching about this problem, I found out that this is related to a malformed response from IAS, as stated in:&lt;BR /&gt;
				-&lt;A href="http://stackoverflow.com/questions/35525715/http-get-parse-error-code-hpe-unexpected-content-length" rel="nofollow"&gt;http://stackoverflow.com/questions/35525715/http-get-parse-error-code-hpe-unexpected-content-length&lt;/A&gt;&lt;/P&gt;

			&lt;P&gt;-&lt;A href="https://github.com/nodejs/node/issues/5754" rel="nofollow"&gt;https://github.com/nodejs/node/issues/5754&lt;/A&gt;&lt;/P&gt;

			&lt;P&gt;-&lt;A href="https://github.com/nodejs/node/issues/6517" rel="nofollow"&gt;https://github.com/nodejs/node/issues/6517&lt;/A&gt;&lt;BR /&gt;
				&amp;nbsp;&lt;/P&gt;

			&lt;P&gt;As a workaround, I had to use a module based on curl. Can anyone please explain me if this format of the response from IAS could be "fixed" and avoid future problems with other developers?&lt;/P&gt;

			&lt;P&gt;Thank you.&lt;/P&gt;
		&lt;/DIV&gt;
	&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 22 Aug 2017 19:23:22 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Confidential-Computing/Remote-Attestation-Process-problem-with-IAS-response/m-p/1171303#M3214</guid>
      <dc:creator>Dalton_V_</dc:creator>
      <dc:date>2017-08-22T19:23:22Z</dc:date>
    </item>
    <item>
      <title>Dalton, I will try to</title>
      <link>https://community.intel.com/t5/Intel-Confidential-Computing/Remote-Attestation-Process-problem-with-IAS-response/m-p/1171304#M3215</link>
      <description>&lt;P&gt;Dalton, I will try to recreate this error of&amp;nbsp;HPE_UNEXPECTED_CONTENT_LENGTH on my development environment to understand this issue better on when and how it can occur. A status update will be followed.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Sep 2017 16:59:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Confidential-Computing/Remote-Attestation-Process-problem-with-IAS-response/m-p/1171304#M3215</guid>
      <dc:creator>Hoang_N_Intel</dc:creator>
      <dc:date>2017-09-26T16:59:45Z</dc:date>
    </item>
  </channel>
</rss>

