<?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 HTTP Monitor - Connection keep alive or close by default? in Synthetic Monitoring</title>
    <link>https://community.dynatrace.com/t5/Synthetic-Monitoring/HTTP-Monitor-Connection-keep-alive-or-close-by-default/m-p/252063#M2538</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have 2 questions concerning HTTP monitors :&lt;/P&gt;&lt;P&gt;- HTTP calls are all HTTP 1.1 or not?&lt;BR /&gt;- By default, connection are closed in HTTP Monitors?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I understand why, but, as persistent connections are the default behavior of any connection in HTTP 1.1, the behavior is different :&lt;/P&gt;&lt;P&gt;recently we had issue with one HTTP Monitor, which is calling only one url.&lt;BR /&gt;Suddenly, every time, we got a connection refused.&lt;BR /&gt;I created its brower clickpath version: no error.&lt;BR /&gt;We discovered at the end, that it was due to a connection closed.&lt;BR /&gt;I added in the request header, connection: keep-alive and it was ok.&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Sabine&lt;/P&gt;</description>
    <pubDate>Wed, 31 Jul 2024 08:18:46 GMT</pubDate>
    <dc:creator>SabineR</dc:creator>
    <dc:date>2024-07-31T08:18:46Z</dc:date>
    <item>
      <title>HTTP Monitor - Connection keep alive or close by default?</title>
      <link>https://community.dynatrace.com/t5/Synthetic-Monitoring/HTTP-Monitor-Connection-keep-alive-or-close-by-default/m-p/252063#M2538</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have 2 questions concerning HTTP monitors :&lt;/P&gt;&lt;P&gt;- HTTP calls are all HTTP 1.1 or not?&lt;BR /&gt;- By default, connection are closed in HTTP Monitors?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I understand why, but, as persistent connections are the default behavior of any connection in HTTP 1.1, the behavior is different :&lt;/P&gt;&lt;P&gt;recently we had issue with one HTTP Monitor, which is calling only one url.&lt;BR /&gt;Suddenly, every time, we got a connection refused.&lt;BR /&gt;I created its brower clickpath version: no error.&lt;BR /&gt;We discovered at the end, that it was due to a connection closed.&lt;BR /&gt;I added in the request header, connection: keep-alive and it was ok.&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Sabine&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2024 08:18:46 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Synthetic-Monitoring/HTTP-Monitor-Connection-keep-alive-or-close-by-default/m-p/252063#M2538</guid>
      <dc:creator>SabineR</dc:creator>
      <dc:date>2024-07-31T08:18:46Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP Monitor - Connection keep alive or close by default?</title>
      <link>https://community.dynatrace.com/t5/Synthetic-Monitoring/HTTP-Monitor-Connection-keep-alive-or-close-by-default/m-p/252625#M2543</link>
      <description>&lt;P&gt;Yes we close the connection and you need to add the keep-alive header in this case.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Aug 2024 08:26:32 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Synthetic-Monitoring/HTTP-Monitor-Connection-keep-alive-or-close-by-default/m-p/252625#M2543</guid>
      <dc:creator>hadeer_diwan</dc:creator>
      <dc:date>2024-08-06T08:26:32Z</dc:date>
    </item>
  </channel>
</rss>

