# Hard coded request for HTTP in Designer Launcher even if gateway set up for HTTPS

**URL:** <https://forum.inductiveautomation.com/t/hard-coded-request-for-http-in-designer-launcher-even-if-gateway-set-up-for-https/34027>\
**Category:** Ignition Early Access\
**Created:** [April 18, 2020, 12:05pm UTC](https://forum.inductiveautomation.com/t/hard-coded-request-for-http-in-designer-launcher-even-if-gateway-set-up-for-https/34027 "2020-04-18T12:05:27Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [May 26, 2021, 2:31pm UTC](https://forum.inductiveautomation.com/t/hard-coded-request-for-http-in-designer-launcher-even-if-gateway-set-up-for-https/34027/11 "2021-05-26T14:31:52Z")

</div>

Designer Launcher in 8.1.6 now uses `/StatusPing` directly, so you will no longer need the explicit rewrite. Thankfully, you can also use the new launcher for older gateways that you’ve not yet upgraded since the issue was resolved in the launcher itself.

---

_[View the full topic](https://forum.inductiveautomation.com/t/hard-coded-request-for-http-in-designer-launcher-even-if-gateway-set-up-for-https/34027)._