<?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>zephyr: Recommended way to run a HTTPS server</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/74937/zephyr-recommended-way-to-run-a-https-server</link><description>We are using Zephyr RTOS running on a nRF9160 MCU. One requirement of our project is to run a local HTTPS webserver on the target. Our investigation showed that the recommended webserver for Zephyr is civetweb. However civetweb under Zephyr does not support</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 10 May 2021 14:35:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/74937/zephyr-recommended-way-to-run-a-https-server" /><item><title>RE: zephyr: Recommended way to run a HTTPS server</title><link>https://devzone.nordicsemi.com/thread/309029?ContentTypeID=1</link><pubDate>Mon, 10 May 2021 14:35:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ee4442ee-e8a1-4b18-b36a-6c76d49977fd</guid><dc:creator>Didrik Rokhaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
[quote user=""]What is Nordics recommended way to run a HTTPS-Server on Zephyr?[/quote]
&lt;p&gt;&amp;nbsp;We don&amp;#39;t have any, as far as I know.&lt;/p&gt;
&lt;p&gt;A big reason for this is that cellular devices usually are behind both a NAT layer and a firewall, which makes it hard to send an IP packet to the device without the device initiating the communication.&lt;/p&gt;
&lt;p&gt;Then, if this problem is overcome somehow, you would have to deal with the power consumption which comes with having to listen for incoming connections all the time.&lt;/p&gt;
&lt;p&gt;However, if you have a way to solve these two challenges, it should be possible to run a HTTPS server on the nRF9160.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;On the most basic level, you can open a TLS socket, and handle everything yourself. If your needs are simple, this might not be too much work.&lt;/p&gt;
&lt;p&gt;If you can find HTTP(S) servers where you provide the socket, those should also work.&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></channel></rss>