<?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 Using &amp;quot;content-type&amp;quot; or &amp;quot;Content-Type&amp;quot; header in API REST in Nuxeo Forum</title>
    <link>https://connect.hyland.com/t5/nuxeo-forum/using-quot-content-type-quot-or-quot-content-type-quot-header-in/m-p/317050#M4051</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;(Nuxeo 6.0)&lt;/P&gt;
&lt;P&gt;I observe that sometimes Nuxeo is happy with a "content-type" entry in the header and sometimes it is happy with "Content-Type"&lt;/P&gt;
&lt;P&gt;Is there a clear rule ?&lt;/P&gt;
&lt;P&gt;examples:&lt;/P&gt;
&lt;P&gt;id/&lt;UID&gt;/@op/Document.SetLifeCycle is fine with "Content-Type"&lt;/UID&gt;&lt;/P&gt;
&lt;P&gt;whereas&lt;/P&gt;
&lt;P&gt;group/search?q=&lt;QUERY&gt; &amp;amp; currentPageIndex=&lt;PAGE&gt; &amp;amp;pageize=1000 is fine with "content-type"&lt;/PAGE&gt;&lt;/QUERY&gt;&lt;/P&gt;
&lt;P&gt;Can you indicate the rule (or please select ONE policy)&lt;/P&gt;
&lt;P&gt;Regards
Christian&lt;/P&gt;</description>
    <pubDate>Fri, 11 Mar 2016 16:43:15 GMT</pubDate>
    <dc:creator>Arnault_</dc:creator>
    <dc:date>2016-03-11T16:43:15Z</dc:date>
    <item>
      <title>Using "content-type" or "Content-Type" header in API REST</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/using-quot-content-type-quot-or-quot-content-type-quot-header-in/m-p/317050#M4051</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;(Nuxeo 6.0)&lt;/P&gt;
&lt;P&gt;I observe that sometimes Nuxeo is happy with a "content-type" entry in the header and sometimes it is happy with "Content-Type"&lt;/P&gt;
&lt;P&gt;Is there a clear rule ?&lt;/P&gt;
&lt;P&gt;examples:&lt;/P&gt;
&lt;P&gt;id/&lt;UID&gt;/@op/Document.SetLifeCycle is fine with "Content-Type"&lt;/UID&gt;&lt;/P&gt;
&lt;P&gt;whereas&lt;/P&gt;
&lt;P&gt;group/search?q=&lt;QUERY&gt; &amp;amp; currentPageIndex=&lt;PAGE&gt; &amp;amp;pageize=1000 is fine with "content-type"&lt;/PAGE&gt;&lt;/QUERY&gt;&lt;/P&gt;
&lt;P&gt;Can you indicate the rule (or please select ONE policy)&lt;/P&gt;
&lt;P&gt;Regards
Christian&lt;/P&gt;</description>
      <pubDate>Fri, 11 Mar 2016 16:43:15 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/using-quot-content-type-quot-or-quot-content-type-quot-header-in/m-p/317050#M4051</guid>
      <dc:creator>Arnault_</dc:creator>
      <dc:date>2016-03-11T16:43:15Z</dc:date>
    </item>
    <item>
      <title>Re: Using "content-type" or "Content-Type" header in API REST</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/using-quot-content-type-quot-or-quot-content-type-quot-header-in/m-p/317051#M4052</link>
      <description>&lt;P&gt;Thanks for this helpful answer&lt;/P&gt;</description>
      <pubDate>Thu, 31 Mar 2016 13:14:43 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/using-quot-content-type-quot-or-quot-content-type-quot-header-in/m-p/317051#M4052</guid>
      <dc:creator>Arnault_</dc:creator>
      <dc:date>2016-03-31T13:14:43Z</dc:date>
    </item>
  </channel>
</rss>

