<?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: wraparound180 causes 414 error in ArcGIS Viewer for Flex Questions</title>
    <link>https://community.esri.com/t5/arcgis-viewer-for-flex-questions/wraparound180-causes-414-error/m-p/372743#M10613</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Robert, that looks like it will solve the issue!&amp;nbsp; We will try the proxy page.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 May 2015 20:07:55 GMT</pubDate>
    <dc:creator>JimNoel</dc:creator>
    <dc:date>2015-05-13T20:07:55Z</dc:date>
    <item>
      <title>wraparound180 causes 414 error</title>
      <link>https://community.esri.com/t5/arcgis-viewer-for-flex-questions/wraparound180-causes-414-error/m-p/372741#M10611</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt; font-family: 'Calibri',sans-serif;"&gt;We recently added the “wraparound180” parameter to the &amp;lt;map&amp;gt; tag for our FlexViewer site&lt;/SPAN&gt;&lt;SPAN style="font-size: 12.0pt; font-family: 'Calibri',sans-serif;"&gt; to allow our features that straddle the 180E line to display together.&amp;nbsp; (We're using the WGS 1984 Web Mercator projection.)&amp;nbsp; This has resulted in a problem:&amp;nbsp; The layers on our server are no longer displaying.&amp;nbsp; &lt;SPAN style="font-size: 12.0pt; font-family: 'Calibri',sans-serif;"&gt;On studying the HTTP traffic, we find that when the layer fails to display, it is due to a “414 Request-URI Too Long” error.&amp;nbsp; Looking at the request parameters, this seems to be a result of the “bboxSR” and “imageSR” parameters being much longer than usual.&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt; font-family: 'Calibri',sans-serif;"&gt;Normally, “bboxSR” and “imageSR” just have the &lt;SPAN style="font-family: Calibri, sans-serif; font-size: 16px;"&gt;the spatial reference ID of 3587.&amp;nbsp; However, when using &lt;SPAN style="font-family: Calibri, sans-serif; font-size: 16px;"&gt;wraparound180&lt;/SPAN&gt;&lt;/SPAN&gt;, these parameters are given the full spatial reference description rather than spatial reference ID.&amp;nbsp; As a result, the HTTP request is more than 2000 characters long, which causes the 414 error on our server.&amp;nbsp; Does anyone know why &lt;SPAN style="font-family: Calibri, sans-serif; font-size: 16px;"&gt;wraparound180 uses the full spatial description rather than spatial ID?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 16px; font-family: Calibri, sans-serif;"&gt;I had someone put a version of one our map services on a different server, and the long request worked fine there, so apparently using spatial description rather than spatial ID is "legal".&amp;nbsp; So w&lt;/SPAN&gt;&lt;SPAN style="font-size: 12.0pt; font-family: 'Calibri',sans-serif;"&gt;&lt;SPAN&gt;e're looking into having our server configured to allow longer HTTP requests. However, we haven't had success with that yet.&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt; font-family: 'Calibri',sans-serif;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt; font-family: 'Calibri',sans-serif;"&gt;&lt;SPAN&gt;Another approach I thought about was changing the layer requests from GET to POST.&amp;nbsp; (GET seems to be the default.)&amp;nbsp; Is there a way of configuring the Viewer so it uses the POST method rather than GET?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt; font-family: 'Calibri',sans-serif;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt; font-family: 'Calibri',sans-serif;"&gt;&lt;SPAN&gt;We also have a website that uses the ArcGIS Flex API (rather than FlexViewer), so I would also like to know if the map object or ArcGISDynamicMapServiceLayer can be set to use the POST method.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt; font-family: 'Calibri',sans-serif;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt; font-family: 'Calibri',sans-serif;"&gt;&lt;SPAN&gt;Thanks!&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 May 2015 19:38:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-viewer-for-flex-questions/wraparound180-causes-414-error/m-p/372741#M10611</guid>
      <dc:creator>JimNoel</dc:creator>
      <dc:date>2015-05-12T19:38:23Z</dc:date>
    </item>
    <item>
      <title>Re: wraparound180 causes 414 error</title>
      <link>https://community.esri.com/t5/arcgis-viewer-for-flex-questions/wraparound180-causes-414-error/m-p/372742#M10612</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jim,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Using a proxy for your app would get you past this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Viewer:&lt;/P&gt;&lt;P&gt;&lt;A href="http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#/Using_a_proxy_page/01m30000000w000000/" title="http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#/Using_a_proxy_page/01m30000000w000000/"&gt;ArcGIS Viewer for Flex - using a proxy page&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;API:&lt;/P&gt;&lt;P&gt;&lt;A href="https://developers.arcgis.com/flex/guide/using-the-proxy-page.htm" title="https://developers.arcgis.com/flex/guide/using-the-proxy-page.htm"&gt;Using the proxy page—ArcGIS API for Flex | ArcGIS for Developers&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or you could change your web servers url length limit:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.mytecbits.com/microsoft/iis/iis-changing-maxquerystring-and-maxurl" title="http://www.mytecbits.com/microsoft/iis/iis-changing-maxquerystring-and-maxurl"&gt;IIS: Changing maxQueryString and maxUrl | My Tec Bits.&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 May 2015 21:12:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-viewer-for-flex-questions/wraparound180-causes-414-error/m-p/372742#M10612</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2015-05-12T21:12:08Z</dc:date>
    </item>
    <item>
      <title>Re: wraparound180 causes 414 error</title>
      <link>https://community.esri.com/t5/arcgis-viewer-for-flex-questions/wraparound180-causes-414-error/m-p/372743#M10613</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Robert, that looks like it will solve the issue!&amp;nbsp; We will try the proxy page.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2015 20:07:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-viewer-for-flex-questions/wraparound180-causes-414-error/m-p/372743#M10613</guid>
      <dc:creator>JimNoel</dc:creator>
      <dc:date>2015-05-13T20:07:55Z</dc:date>
    </item>
  </channel>
</rss>

