<?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: Adding custom http headers to tRESTResponse in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Adding-custom-http-headers-to-tRESTResponse/m-p/2218596#M13736</link>
    <description>This enhancement has been implemented in version 5.2. See tRESTResponse/Advanced Settings to add manual http headers.
&lt;BR /&gt;For CORS, just add the http header "Access-Control-Allow-Origin" with the value "*" to the tRESRResponse component.</description>
    <pubDate>Tue, 09 Oct 2012 13:17:28 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2012-10-09T13:17:28Z</dc:date>
    <item>
      <title>Adding custom http headers to tRESTResponse</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Adding-custom-http-headers-to-tRESTResponse/m-p/2218595#M13735</link>
      <description>Is it possible to add custom http headers to a tRESTResponse? I know that there is an enhancement request for doing this and it is still not in progress of being worked on ( 
&lt;A href="https://jira.talendforge.org/browse/TESB-6057" target="_blank" rel="nofollow noopener noreferrer"&gt;https://jira.talendforge.org/browse/TESB-6057&lt;/A&gt;). I would need this so that I can implement CORS. I do not wish to use JSONP since it would require more logic and be more of a "work-around". 
&lt;BR /&gt;Could I add http headers using tGroovy or tJavaFlex?</description>
      <pubDate>Sat, 06 Oct 2012 15:45:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Adding-custom-http-headers-to-tRESTResponse/m-p/2218595#M13735</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-10-06T15:45:58Z</dc:date>
    </item>
    <item>
      <title>Re: Adding custom http headers to tRESTResponse</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Adding-custom-http-headers-to-tRESTResponse/m-p/2218596#M13736</link>
      <description>This enhancement has been implemented in version 5.2. See tRESTResponse/Advanced Settings to add manual http headers.
&lt;BR /&gt;For CORS, just add the http header "Access-Control-Allow-Origin" with the value "*" to the tRESRResponse component.</description>
      <pubDate>Tue, 09 Oct 2012 13:17:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Adding-custom-http-headers-to-tRESTResponse/m-p/2218596#M13736</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-10-09T13:17:28Z</dc:date>
    </item>
    <item>
      <title>Re: Adding custom http headers to tRESTResponse</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Adding-custom-http-headers-to-tRESTResponse/m-p/2218597#M13737</link>
      <description>Dear Talend ESB Team,&lt;BR /&gt;Using last version of 5.6 in component TRestResponse and adding&amp;nbsp;"Access-Control-Allow-Origin" with the value "*" , we still are getting the same CORS problem.&lt;BR /&gt;Do you know why header is not seen at http response?&lt;BR /&gt;&amp;nbsp;</description>
      <pubDate>Tue, 11 Nov 2014 21:26:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Adding-custom-http-headers-to-tRESTResponse/m-p/2218597#M13737</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-11-11T21:26:37Z</dc:date>
    </item>
    <item>
      <title>Re: Adding custom http headers to tRESTResponse</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Adding-custom-http-headers-to-tRESTResponse/m-p/2218598#M13738</link>
      <description>We restarted Runtime ESB and it worked.</description>
      <pubDate>Wed, 12 Nov 2014 13:19:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Adding-custom-http-headers-to-tRESTResponse/m-p/2218598#M13738</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-11-12T13:19:55Z</dc:date>
    </item>
  </channel>
</rss>

