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

<div class="post-metadata">

**Author:** ![Kevin.Collins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.collins/32/13497_2.png) [@Kevin.Collins](https://forum.inductiveautomation.com/u/Kevin.Collins)\
**Post date:** [August 9, 2020, 4:29am UTC](https://forum.inductiveautomation.com/t/hard-coded-request-for-http-in-designer-launcher-even-if-gateway-set-up-for-https/34027/8 "2020-08-09T04:29:06Z")

</div>

Thanks @Kevin.Herron and @accyroy. I was able to confirm the same as you had that a request towards `/main/StatusPing` was the culprit. I’ve got the same setup in Traefik and was able to mitigate it using the same strategy by applying my container labels (running with Docker) like such:

```auto
labels:
  ...
  - "traefik.http.middlewares.ignition-replacepathmain.replacepathregex.regex=^/main/StatusPing$$"
  - "traefik.http.middlewares.ignition-replacepathmain.replacepathregex.replacement=/StatusPing"
  - "traefik.http.routers.ignition.middlewares=ignition-replacepathmain"

```

Having the reverse proxy perform the substitution instead of the gateway seems to do the trick, just like described above. Thank you both once again!

---

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