<?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 Re: Secure Endpoint API - wrong rate limit headers in Endpoint Security</title>
    <link>https://community.cisco.com/t5/endpoint-security/secure-endpoint-api-wrong-rate-limit-headers/m-p/4973369#M8038</link>
    <description>&lt;P&gt;The fix has been applied to &lt;A href="https://developer.cisco.com/docs/secure-endpoint/#!overview/rate-limits" target="_self"&gt;our documentation&lt;/A&gt;.&amp;nbsp; It is showing X-RateLimit with no extra dash as it appears in the RFC. Thank you for brining this to our attention!&lt;/P&gt;
&lt;P&gt;-Matt&lt;/P&gt;</description>
    <pubDate>Thu, 07 Dec 2023 13:03:46 GMT</pubDate>
    <dc:creator>Matthew Franks</dc:creator>
    <dc:date>2023-12-07T13:03:46Z</dc:date>
    <item>
      <title>Secure Endpoint API - wrong rate limit headers</title>
      <link>https://community.cisco.com/t5/endpoint-security/secure-endpoint-api-wrong-rate-limit-headers/m-p/4969592#M8031</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;I noticed a minor error in the &lt;A href="https://developer.cisco.com/docs/secure-endpoint/#!overview/rate-limits" target="_self"&gt;Secure Endpoint API documentation&lt;/A&gt;&amp;nbsp;that I wanted to bring to your attention.&lt;BR /&gt;The HTTP response headers are listed as&lt;/P&gt;&lt;PRE&gt;X-Rate-Limit-*&lt;/PRE&gt;&lt;P&gt;but when I tried calling "&lt;A href="https://api.eu.amp.cisco.com/v1/computers" target="_blank"&gt;https://api.eu.amp.cisco.com/v1/computers&lt;/A&gt;", the API returned&lt;/P&gt;&lt;PRE&gt;X-RateLimit-*&lt;/PRE&gt;&lt;P&gt;without the dash in the middle. Just wanted to give you a heads up &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Dec 2023 06:38:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/endpoint-security/secure-endpoint-api-wrong-rate-limit-headers/m-p/4969592#M8031</guid>
      <dc:creator>Bunged</dc:creator>
      <dc:date>2023-12-01T06:38:12Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Endpoint API - wrong rate limit headers</title>
      <link>https://community.cisco.com/t5/endpoint-security/secure-endpoint-api-wrong-rate-limit-headers/m-p/4969828#M8033</link>
      <description>&lt;P&gt;Thank you for reporting this. I'll file an issue with the documentation team.&lt;/P&gt;
&lt;P&gt;-Matt&lt;/P&gt;</description>
      <pubDate>Fri, 01 Dec 2023 13:23:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/endpoint-security/secure-endpoint-api-wrong-rate-limit-headers/m-p/4969828#M8033</guid>
      <dc:creator>Matthew Franks</dc:creator>
      <dc:date>2023-12-01T13:23:58Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Endpoint API - wrong rate limit headers</title>
      <link>https://community.cisco.com/t5/endpoint-security/secure-endpoint-api-wrong-rate-limit-headers/m-p/4973369#M8038</link>
      <description>&lt;P&gt;The fix has been applied to &lt;A href="https://developer.cisco.com/docs/secure-endpoint/#!overview/rate-limits" target="_self"&gt;our documentation&lt;/A&gt;.&amp;nbsp; It is showing X-RateLimit with no extra dash as it appears in the RFC. Thank you for brining this to our attention!&lt;/P&gt;
&lt;P&gt;-Matt&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2023 13:03:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/endpoint-security/secure-endpoint-api-wrong-rate-limit-headers/m-p/4973369#M8038</guid>
      <dc:creator>Matthew Franks</dc:creator>
      <dc:date>2023-12-07T13:03:46Z</dc:date>
    </item>
  </channel>
</rss>

