<?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>Question Re: HTTPS in a chunked conecction in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/https-in-a-chunked-conecction/qaa-p/12276131#M4599110</link>
    <description>&lt;P&gt;Because you can't keep the connection open permanently. You might poll the external system from CPI, say every minute or so.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Morten&lt;/P&gt;</description>
    <pubDate>Fri, 24 Jul 2020 11:45:50 GMT</pubDate>
    <dc:creator>MortenWittrock</dc:creator>
    <dc:date>2020-07-24T11:45:50Z</dc:date>
    <item>
      <title>HTTPS in a chunked conecction</title>
      <link>https://community.sap.com/t5/technology-q-a/https-in-a-chunked-conecction/qaq-p/12276128</link>
      <description>&lt;P&gt;Help to capture the response that is sent by HTTPS in a chunked conecction ...&lt;/P&gt; 
  &lt;PRE&gt;&lt;CODE&gt;Currently we retrieve it by CMD command console, attached image.

curl --user Admin:password –raw &lt;A href="https://srs.xxxx" target="test_blank"&gt;https://srs.xxxx&lt;/A&gt;

This persistent line should always be active, waiting for a response.


How to create the persistent line in SAP CPI. Q always activates the response, so that CPI captures it.???


CPI
Integratio Flow

What could it take to always have the persistent line active?



Outcome
The capture was made, but it is not constant ...




Can someone help us community?


Thanks.


&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 22 Jul 2020 17:47:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/https-in-a-chunked-conecction/qaq-p/12276128</guid>
      <dc:creator>former_member692208</dc:creator>
      <dc:date>2020-07-22T17:47:18Z</dc:date>
    </item>
    <item>
      <title>Re: HTTPS in a chunked conecction</title>
      <link>https://community.sap.com/t5/technology-q-a/https-in-a-chunked-conecction/qaa-p/12276129#M4599108</link>
      <description>&lt;P&gt;Hi Arturo&lt;/P&gt;&lt;P&gt;That HTTP connection will time out sooner or later. Is having the events pushed to CPI not an option?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Morten&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jul 2020 18:56:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/https-in-a-chunked-conecction/qaa-p/12276129#M4599108</guid>
      <dc:creator>MortenWittrock</dc:creator>
      <dc:date>2020-07-22T18:56:40Z</dc:date>
    </item>
    <item>
      <title>Re: HTTPS in a chunked conecction</title>
      <link>https://community.sap.com/t5/technology-q-a/https-in-a-chunked-conecction/qaa-p/12276130#M4599109</link>
      <description>&lt;P&gt;Thank you, Morten Wittrock,&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;Why won't sending them by CPI be an option?&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 23 Jul 2020 15:53:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/https-in-a-chunked-conecction/qaa-p/12276130#M4599109</guid>
      <dc:creator>former_member692208</dc:creator>
      <dc:date>2020-07-23T15:53:20Z</dc:date>
    </item>
    <item>
      <title>Re: HTTPS in a chunked conecction</title>
      <link>https://community.sap.com/t5/technology-q-a/https-in-a-chunked-conecction/qaa-p/12276131#M4599110</link>
      <description>&lt;P&gt;Because you can't keep the connection open permanently. You might poll the external system from CPI, say every minute or so.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Morten&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jul 2020 11:45:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/https-in-a-chunked-conecction/qaa-p/12276131#M4599110</guid>
      <dc:creator>MortenWittrock</dc:creator>
      <dc:date>2020-07-24T11:45:50Z</dc:date>
    </item>
  </channel>
</rss>

