<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:04:58 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[IOTDM-24] Need to update content-type in the headers</title>
                <link>https://jira.opendaylight.org/browse/IOTDM-24</link>
                <project id="10131" key="IOTDM">iotdm</project>
                    <description>&lt;p&gt;6.4.3	Content-Type&lt;br/&gt;
Any HTTP request or response containing message-body shall include the Content-type header set to one of &#8221;application/xml&#8221;, &#8220;application/json&#8221;, &#8221;application/vnd.onem2m-res+xml&#8221;, &#8220;application/vnd.onem2m-res+json&#8221;, &#8220;application/vnd.onem2m-ntfy+xml&#8221; , &#8220;application/vnd.onem2m-ntfy+json&#8221;, &#8220;application/vnd.onem2m-attrs+xml&#8221; , &#8220;application/vnd.onem2m-attrs+json&#8221;.&lt;br/&gt;
Content-Type of the HTTP response should be chosen by the Hosting CSE considering Accept header given in the HTTP request. For example, if the Accept header in a request is set to &#8220;application/vnd.onem2m-prsp+xml&#8221;, then the response should use one of the oneM2M defined media types in XML serialization (see clause 6.7 &lt;span class=&quot;error&quot;&gt;&amp;#91;3&amp;#93;&lt;/span&gt;).&lt;br/&gt;
The value of the Resource Type primitive parameter, which is present in Create request primitives only, shall be appended to the Content-type of the corresponding HTTP request message in the form ty=value, separated by a semicolon character. A valid Content-Type header in this case looks e.g. as follows: &lt;br/&gt;
                                Content-Type: application/vnd.onem2m-res+xml; ty=3&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="19530">IOTDM-24</key>
            <summary>Need to update content-type in the headers</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="ahmed.razi@tcs.com">Razi Ahmed</assignee>
                                    <reporter username="wucangji@gmail.com">Cangji Wu</reporter>
                        <labels>
                    </labels>
                <created>Tue, 4 Aug 2015 04:31:56 +0000</created>
                <updated>Wed, 9 Sep 2015 20:50:02 +0000</updated>
                            <resolved>Wed, 9 Sep 2015 20:50:02 +0000</resolved>
                                    <version>unspecified</version>
                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="35445" author="ahmed.razi@tcs.com" created="Wed, 2 Sep 2015 04:43:27 +0000"  >&lt;p&gt;I was able to provision CSE using &lt;a href=&quot;http://localhost:8181/restconf/operations/onem2m:onem2m-cse-provisioning&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8181/restconf/operations/onem2m:onem2m-cse-provisioning&lt;/a&gt; but when I am provisioning AE from &lt;a href=&quot;http://localhost:8282/mockCSE?ty=2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8282/mockCSE?ty=2&lt;/a&gt;, I am unable to replicate the bug.&lt;/p&gt;

&lt;p&gt;Is there any code change? Can you tell me the URL to provision AE?&lt;/p&gt;</comment>
                            <comment id="35446" author="wucangji@gmail.com" created="Wed, 2 Sep 2015 04:49:12 +0000"  >&lt;p&gt;(In reply to Razi Ahmed from comment #1)&lt;br/&gt;
&amp;gt; I was able to provision CSE using&lt;br/&gt;
&amp;gt; &lt;a href=&quot;http://localhost:8181/restconf/operations/onem2m:onem2m-cse-provisioning&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8181/restconf/operations/onem2m:onem2m-cse-provisioning&lt;/a&gt; but&lt;br/&gt;
&amp;gt; when I am provisioning AE from &lt;a href=&quot;http://localhost:8282/mockCSE?ty=2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8282/mockCSE?ty=2&lt;/a&gt;, I am&lt;br/&gt;
&amp;gt; unable to replicate the bug.&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; Is there any code change? Can you tell me the URL to provision AE?&lt;/p&gt;

&lt;p&gt;This bug has been fixed and it is marked as &quot;WAITING FOR REVIEW&quot;.&lt;br/&gt;
After review, we will mark it as &quot;fixed&quot;.&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;</comment>
                            <comment id="35447" author="wucangji@gmail.com" created="Wed, 2 Sep 2015 04:53:38 +0000"  >&lt;p&gt;(In reply to Razi Ahmed from comment #1)&lt;br/&gt;
&amp;gt; I was able to provision CSE using&lt;br/&gt;
&amp;gt; &lt;a href=&quot;http://localhost:8181/restconf/operations/onem2m:onem2m-cse-provisioning&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8181/restconf/operations/onem2m:onem2m-cse-provisioning&lt;/a&gt; but&lt;br/&gt;
&amp;gt; when I am provisioning AE from &lt;a href=&quot;http://localhost:8282/mockCSE?ty=2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8282/mockCSE?ty=2&lt;/a&gt;, I am&lt;br/&gt;
&amp;gt; unable to replicate the bug.&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; Is there any code change? Can you tell me the URL to provision AE?&lt;/p&gt;

&lt;p&gt;To create AE, you can see the example here within Postman:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://www.getpostman.com/collections/fea43287d54edf0d38a0&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://www.getpostman.com/collections/fea43287d54edf0d38a0&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Do you receive an invite of slack several days ago? I think I invited you.&lt;br/&gt;
You can use the slack to ask us any question.&lt;/p&gt;</comment>
                            <comment id="35448" author="ahmed.razi@tcs.com" created="Thu, 3 Sep 2015 19:09:48 +0000"  >&lt;p&gt;Yes, I got the invite of slack and joined it. I will post any queries on slack from now onward.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>4088</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=4088]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i01mon:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>