# Support for HTTPS?

**URL:** <https://answers.netlify.com/t/support-for-https/333>\
**Category:** Support\
**Tags:** netlify-dev-open-beta, netlify-dns-https-ssl\
**Created:** [April 9, 2019, 7:14pm UTC](https://answers.netlify.com/t/support-for-https/333 "2019-04-09T19:14:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![borisschapira](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/borisschapira/32/214_2.png) [@borisschapira](https://answers.netlify.com/u/borisschapira)\
**Post date:** [April 9, 2019, 7:14pm UTC](https://answers.netlify.com/t/support-for-https/333/1 "2019-04-09T19:14:26Z")

</div>

At the moment, I am developing locally on a HTTPS-certified domain that I generated with [GitHub - FiloSottile/mkcert: A simple zero-config tool to make locally trusted development certificates with any names you'd like.](https://github.com/FiloSottile/mkcert). This way, I can locally test everything that requires a secure site, starting with the Geolocation API and Service Workers. Is there any plan for an HTTPS support in `netlify dev`?

---

<div class="post-metadata">

**Author:** ![swyx](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/swyx/32/269_2.png) [@swyx](https://answers.netlify.com/u/swyx)\
**Post date:** [April 10, 2019, 3:51pm UTC](https://answers.netlify.com/t/support-for-https/333/2 "2019-04-10T15:51:22Z")

</div>

we’ll probably want to support it, yes. i dont know what the plan is at the moment, but its been raised by a few people. are you able to get around it in userland?

---

<div class="post-metadata">

**Author:** ![borisschapira](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/borisschapira/32/214_2.png) [@borisschapira](https://answers.netlify.com/u/borisschapira)\
**Post date:** [April 10, 2019, 4:36pm UTC](https://answers.netlify.com/t/support-for-https/333/3 "2019-04-10T16:36:29Z")

</div>

Without Netlify Dev, yes, I still use my elaborated `jekyll serve`:

```auto
JEKYLL_ENV=development jekyll serve --ssl-key ./boris.schapira.local+3-key.pem --ssl-cert ./boris.schapira.local+3.pem

```

with my custom cert.

With Netlify Dev, no, I don’t know how to make things work out.

---

<div class="post-metadata">

**Author:** ![calavera](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/calavera/32/8275_2.png) [@calavera](https://answers.netlify.com/u/calavera)\
**Post date:** [April 17, 2019, 10:05pm UTC](https://answers.netlify.com/t/support-for-https/333/4 "2019-04-17T22:05:13Z")

</div>

Can you open an issue in [GitHub - netlify/netlify-dev-plugin: Local dev server with functions, rules engine and add-on support](http://github.com/netlify/netlify-dev-plugin)? That would help us track this issue better. I think making local TLS optional should not be complicated, but it requires some thoughts around propagating certificates correctly and ensuring that all the http endpoints use secure connections.

---

<div class="post-metadata">

**Author:** ![borisschapira](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/borisschapira/32/214_2.png) [@borisschapira](https://answers.netlify.com/u/borisschapira)\
**Post date:** [April 17, 2019, 10:27pm UTC](https://answers.netlify.com/t/support-for-https/333/5 "2019-04-17T22:27:57Z")

</div>

Here you are, hope I’ve explained it clearly enough: [Feature request: support secure HTTPS local dev environnement · Issue #455 · netlify/cli · GitHub](https://github.com/netlify/netlify-dev-plugin/issues/137)