# 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:** 9

<div class="post-metadata">

**Author:** ![tom1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tom1/32/21417_2.png) [@tom1](https://forum.inductiveautomation.com/u/tom1)\
**Post date:** [April 5, 2021, 11:53pm UTC](https://forum.inductiveautomation.com/t/hard-coded-request-for-http-in-designer-launcher-even-if-gateway-set-up-for-https/34027/9 "2021-04-05T23:53:54Z")

</div>

I ran into this same issue. Using the same approach as @accyroy in Nginx worked but this seems like something that should be addressed in the Ignition Gateway.

For reference, adding this line to the `location` section of the Nginx configuration works:

```auto
   rewrite ^/main/StatusPing$ /StatusPing;

```

---

_[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)._