<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nRF9160 Serial LTE Modem v1.9.0: Confusion in HTTP Response Documentation</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/85219/nrf9160-serial-lte-modem-v1-9-0-confusion-in-http-response-documentation</link><description>Hi Nordic Team, 
 I noticed a potential issue while migrating from SLM v1.4.0 to v1.9.0. In addition to the inversion of the &amp;lt;state&amp;gt; representation in #XHTTPCRSP introduced in v1.6.0, I understand that the HTTP response headers and body are now transferred</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 07 Mar 2022 09:22:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/85219/nrf9160-serial-lte-modem-v1-9-0-confusion-in-http-response-documentation" /><item><title>RE: nRF9160 Serial LTE Modem v1.9.0: Confusion in HTTP Response Documentation</title><link>https://devzone.nordicsemi.com/thread/356514?ContentTypeID=1</link><pubDate>Mon, 07 Mar 2022 09:22:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f78404a3-1fc6-41e5-a8e9-cbeac484a758</guid><dc:creator>Didrik Rokhaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This PR should address your feedback: &lt;a href="https://github.com/nrfconnect/sdk-nrf/pull/7019"&gt;https://github.com/nrfconnect/sdk-nrf/pull/7019&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Didrik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 Serial LTE Modem v1.9.0: Confusion in HTTP Response Documentation</title><link>https://devzone.nordicsemi.com/thread/355648?ContentTypeID=1</link><pubDate>Tue, 01 Mar 2022 17:16:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dcd9cbd9-3003-4853-b850-c8035ab5d7ab</guid><dc:creator>Macro Yau</dc:creator><description>&lt;p&gt;Thanks for following up!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 Serial LTE Modem v1.9.0: Confusion in HTTP Response Documentation</title><link>https://devzone.nordicsemi.com/thread/355647?ContentTypeID=1</link><pubDate>Tue, 01 Mar 2022 17:10:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6075492b-90cc-4328-aeff-613c95c51657</guid><dc:creator>Didrik Rokhaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I agree that having the state field set to 1 in multiple URCs can be confusing.&lt;/p&gt;
&lt;p&gt;I have informed the developers, and asked them to take the necessary actions.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Didrik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 Serial LTE Modem v1.9.0: Confusion in HTTP Response Documentation</title><link>https://devzone.nordicsemi.com/thread/355166?ContentTypeID=1</link><pubDate>Mon, 28 Feb 2022 06:03:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:10994945-8c45-4e7b-aff5-9fbe74ffbab1</guid><dc:creator>Macro Yau</dc:creator><description>&lt;p&gt;On a related note, the example in NCS documentation shows a &amp;quot;OK&amp;quot; after HTTP request payload data input (and preceding #XHTTPCREQ: 0), but this is not observed on actual hardware (see the AT transcripts above).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>