<?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 Web AppBuilder for Developers Print Widget and Proxy in ArcGIS Web AppBuilder Questions</title>
    <link>https://community.esri.com/t5/arcgis-web-appbuilder-questions/web-appbuilder-for-developers-print-widget-and/m-p/315971#M8423</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have an app put together in Web AppBuilder. It contains a secure service. When we have the app configured to not use a proxy, the print widget works fine with the secure service. No issues. However, if we enable the proxy, the secure service functions well with all the other widgets, but it doesn't seem to be playing nice with the print widget. It errors out with the following response (looking at the network tab in firefox's inspect element)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="352935" class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/352935_pastedImage_1.png" style="width: auto; height: auto;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I compare the parameters being passed in both situations, I find that when the proxy is not enabled and the user is forced to login, the parameters passed to the print service include a token whereas the parameters with the proxy enabled fail to include a token for the print service.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="353021" class="image-2 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/353021_pastedImage_3.png" /&gt;&lt;/P&gt;&lt;P&gt;Any ideas on how to get the print widget to work with a secure service when a proxy is being used?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 May 2017 19:56:05 GMT</pubDate>
    <dc:creator>ShaunConway</dc:creator>
    <dc:date>2017-05-22T19:56:05Z</dc:date>
    <item>
      <title>Web AppBuilder for Developers Print Widget and Proxy</title>
      <link>https://community.esri.com/t5/arcgis-web-appbuilder-questions/web-appbuilder-for-developers-print-widget-and/m-p/315971#M8423</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have an app put together in Web AppBuilder. It contains a secure service. When we have the app configured to not use a proxy, the print widget works fine with the secure service. No issues. However, if we enable the proxy, the secure service functions well with all the other widgets, but it doesn't seem to be playing nice with the print widget. It errors out with the following response (looking at the network tab in firefox's inspect element)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="352935" class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/352935_pastedImage_1.png" style="width: auto; height: auto;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I compare the parameters being passed in both situations, I find that when the proxy is not enabled and the user is forced to login, the parameters passed to the print service include a token whereas the parameters with the proxy enabled fail to include a token for the print service.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="353021" class="image-2 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/353021_pastedImage_3.png" /&gt;&lt;/P&gt;&lt;P&gt;Any ideas on how to get the print widget to work with a secure service when a proxy is being used?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 May 2017 19:56:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-web-appbuilder-questions/web-appbuilder-for-developers-print-widget-and/m-p/315971#M8423</guid>
      <dc:creator>ShaunConway</dc:creator>
      <dc:date>2017-05-22T19:56:05Z</dc:date>
    </item>
  </channel>
</rss>

