<?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 Token bloat in ArcGIS Online Developers Questions</title>
    <link>https://community.esri.com/t5/arcgis-online-developers-questions/token-bloat/m-p/639568#M775</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;When you make calls to ArcGIS Online (and ArcGIS Server) you have to pass a token as a URL argument.&amp;nbsp; The problem with that is that tokens are large.&amp;nbsp; That is a problem because there is a magic size past which HTTP GET operations have to be converted to HTTP POST in order to avoid size limitations.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I was reading the following:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://bugsnag.com/docs/api"&gt;https://bugsnag.com/docs/api&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The thing that is interesting here is the ability to put the token in the authorization header.&amp;nbsp; I am thinking that if ArcGIS * supported this then it would be more efficient because HTTP GET operations can be cached, i.e. more performant.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 21 Sep 2013 10:58:31 GMT</pubDate>
    <dc:creator>RichardWatson</dc:creator>
    <dc:date>2013-09-21T10:58:31Z</dc:date>
    <item>
      <title>Token bloat</title>
      <link>https://community.esri.com/t5/arcgis-online-developers-questions/token-bloat/m-p/639568#M775</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;When you make calls to ArcGIS Online (and ArcGIS Server) you have to pass a token as a URL argument.&amp;nbsp; The problem with that is that tokens are large.&amp;nbsp; That is a problem because there is a magic size past which HTTP GET operations have to be converted to HTTP POST in order to avoid size limitations.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I was reading the following:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://bugsnag.com/docs/api"&gt;https://bugsnag.com/docs/api&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The thing that is interesting here is the ability to put the token in the authorization header.&amp;nbsp; I am thinking that if ArcGIS * supported this then it would be more efficient because HTTP GET operations can be cached, i.e. more performant.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Sep 2013 10:58:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-developers-questions/token-bloat/m-p/639568#M775</guid>
      <dc:creator>RichardWatson</dc:creator>
      <dc:date>2013-09-21T10:58:31Z</dc:date>
    </item>
  </channel>
</rss>

