<?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 LIKE query wildcards blocked by reverse proxy in ArcGIS REST APIs and Services Questions</title>
    <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/like-query-wildcards-blocked-by-reverse-proxy/m-p/378653#M1807</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We have moved our REST services behind a reverse proxy for additional security. However, any SQL where clause passed to our REST services that contain LIKE statements with percent (%) wildcards are getting blocked by the reverse proxy. Apparently this is a side-effect of the URL normalization that is performed in the reverse proxy to validate that malicious queries are not being passed. It is described under #5 here:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://technet.microsoft.com/en-us/library/bb794802.aspx"&gt;http://technet.microsoft.com/en-us/library/bb794802.aspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am using the queryTask in the JavaScript API to construct the queries, but this problem also appears if I try to directly query the REST service. Our system administrators are reluctant to remove the Verify normalization setting in the reverse proxy. Has anyone else encountered this problem and discovered a workaround?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 Aug 2013 17:08:54 GMT</pubDate>
    <dc:creator>MatthewLawton</dc:creator>
    <dc:date>2013-08-22T17:08:54Z</dc:date>
    <item>
      <title>LIKE query wildcards blocked by reverse proxy</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/like-query-wildcards-blocked-by-reverse-proxy/m-p/378653#M1807</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We have moved our REST services behind a reverse proxy for additional security. However, any SQL where clause passed to our REST services that contain LIKE statements with percent (%) wildcards are getting blocked by the reverse proxy. Apparently this is a side-effect of the URL normalization that is performed in the reverse proxy to validate that malicious queries are not being passed. It is described under #5 here:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://technet.microsoft.com/en-us/library/bb794802.aspx"&gt;http://technet.microsoft.com/en-us/library/bb794802.aspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am using the queryTask in the JavaScript API to construct the queries, but this problem also appears if I try to directly query the REST service. Our system administrators are reluctant to remove the Verify normalization setting in the reverse proxy. Has anyone else encountered this problem and discovered a workaround?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Aug 2013 17:08:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/like-query-wildcards-blocked-by-reverse-proxy/m-p/378653#M1807</guid>
      <dc:creator>MatthewLawton</dc:creator>
      <dc:date>2013-08-22T17:08:54Z</dc:date>
    </item>
  </channel>
</rss>

