<?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: tRest using OData URL with blank space in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/tRest-using-OData-URL-with-blank-space/m-p/2317737#M88145</link>
    <description>&lt;P&gt;That may have fixed your issue, but it is not the solution if other people hit the same problem. Your spaces were the only illegal characters in this URL. However any of these used as data would cause issues....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;; / ? : @ = &amp;amp;" &amp;lt; &amp;gt; # % { } | \ ^ ~ [ ] `&lt;/P&gt;</description>
    <pubDate>Wed, 09 May 2018 14:51:31 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2018-05-09T14:51:31Z</dc:date>
    <item>
      <title>tRest using OData URL with blank space</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tRest-using-OData-URL-with-blank-space/m-p/2317734#M88142</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have&amp;nbsp;an issue using tRest component to send&amp;nbsp;an OData query,&amp;nbsp;with a filter like "CFISCYEAR eq 2018" in my URL because of the blank spaces.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My URL is like :&lt;/P&gt;&lt;P&gt;&lt;EM&gt;"&lt;A href="https://myaccount.mysite.com/myreportQueryResults?$" target="_blank" rel="nofollow noopener noreferrer"&gt;https://myaccount.mysite.com/myreportQueryResults?$&lt;/A&gt;&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;&lt;U&gt;filter=CFISCYEAR eq 2018&lt;/U&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&amp;amp;$select=CFISCYEAR,CPROJECT,CPROOBJECT"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;All is working fine without the red part&amp;nbsp;&lt;EM&gt;&lt;FONT color="#FF0000"&gt;&lt;U&gt;filter=CFISCYEAR eq 2018&lt;/U&gt;&lt;/FONT&gt;&lt;/EM&gt;&lt;FONT color="#000000"&gt;.&amp;nbsp;&lt;/FONT&gt;Because of the spaces I have in this filter, I get a&amp;nbsp;java.lang error :&lt;FONT color="#FF0000"&gt;&lt;EM&gt;&amp;nbsp;IllegalArgumentException: Illegal character in query at index XX.&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;It's not not working even after encoding the URL to UTF-8 with URLEncoder, as I get the following error :&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;&lt;EM&gt;com.sun.jersey.api.client.ClientHandlerException: java.lang.IllegalArgumentException: URI is not absolute&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Thanks in advance for your precious replies :=)&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 09 May 2018 14:00:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tRest-using-OData-URL-with-blank-space/m-p/2317734#M88142</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-05-09T14:00:37Z</dc:date>
    </item>
    <item>
      <title>Re: tRest using OData URL with blank space</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tRest-using-OData-URL-with-blank-space/m-p/2317735#M88143</link>
      <description>&lt;P&gt;Thanks, I resolved it.&lt;/P&gt;&lt;P&gt;I replaced the blank space with %20, and it worked.&lt;/P&gt;</description>
      <pubDate>Wed, 09 May 2018 14:42:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tRest-using-OData-URL-with-blank-space/m-p/2317735#M88143</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-05-09T14:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: tRest using OData URL with blank space</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tRest-using-OData-URL-with-blank-space/m-p/2317736#M88144</link>
      <description>&lt;P&gt;This is combination of issues. I'll explain. First of all, you DO need to use the URLEncoder but just for certain parts. You *can* just replace those parts if you are hardcoding the URL, but URLEncoder is probably best to use. You do NOT need to encode the code in green, you DO need to encode the code in red .....&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;EM&gt;"&lt;FONT color="#00FF00"&gt;&lt;STRONG&gt;&lt;A href="https://myaccount.mysite.com/myreportQueryResults?$" target="_blank" rel="nofollow noopener noreferrer"&gt;https://myaccount.mysite.com/myreportQueryResults?$&lt;/A&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;&lt;U&gt;&lt;FONT color="#00FF00"&gt;&lt;STRONG&gt;filter=&lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT color="#FF0000"&gt;CFISCYEAR eq 2018&lt;/FONT&gt;&lt;/U&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT color="#00FF00"&gt;&amp;amp;$select=&lt;/FONT&gt;&lt;FONT color="#FF0000"&gt;CFISCYEAR,CPROJECT,CPROOBJECT&lt;/FONT&gt;"&lt;/EM&gt;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;EM&gt;It is all to do with safe, reserved and unsafe characters. It is described here reasonably well (&lt;A href="https://perishablepress.com/stop-using-unsafe-characters-in-urls/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://perishablepress.com/stop-using-unsafe-characters-in-urls/&lt;/A&gt;).&lt;/EM&gt;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;EM&gt;The reason you hit the second problem is that you encoded the whole thing including the https://. That is why you got the second error.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 09 May 2018 14:48:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tRest-using-OData-URL-with-blank-space/m-p/2317736#M88144</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-05-09T14:48:31Z</dc:date>
    </item>
    <item>
      <title>Re: tRest using OData URL with blank space</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tRest-using-OData-URL-with-blank-space/m-p/2317737#M88145</link>
      <description>&lt;P&gt;That may have fixed your issue, but it is not the solution if other people hit the same problem. Your spaces were the only illegal characters in this URL. However any of these used as data would cause issues....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;; / ? : @ = &amp;amp;" &amp;lt; &amp;gt; # % { } | \ ^ ~ [ ] `&lt;/P&gt;</description>
      <pubDate>Wed, 09 May 2018 14:51:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tRest-using-OData-URL-with-blank-space/m-p/2317737#M88145</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-05-09T14:51:31Z</dc:date>
    </item>
    <item>
      <title>Re: tRest using OData URL with blank space</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tRest-using-OData-URL-with-blank-space/m-p/2317738#M88146</link>
      <description>&lt;P&gt;Hello ! Could you tell us please how did you deal with authentification token for ODATA querry ?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2019 14:14:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tRest-using-OData-URL-with-blank-space/m-p/2317738#M88146</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-07-02T14:14:44Z</dc:date>
    </item>
  </channel>
</rss>

