* This is one of the reasons why it's very useful when the same TLS Termination Proxy also takes care of the certificate renewal process.

                            len += 2;
                            if (len > 256) {
                                throw new RuntimeException("zero termination not found");
                            }
                        }
                        server.oemDomainName = new String(buffer, bufferIndex, len, UNI_ENCODING);
                    } else {

```
.
├── app
│   ├── __init__.py
│   └── main.py
├── Dockerfile
└── requirements.txt
```

#### Behind a TLS Termination Proxy { #behind-a-tls-termination-proxy }

And there has to be something in charge of **renewing the HTTPS certificates**, it could be the same component or it could be something different.

### Example Tools for HTTPS { #example-tools-for-https }

Some of the tools you could use as a TLS Termination Proxy are:

* Traefik
    * Automatically handles certificates renewals ✨

In most cases you would (and should) have a "termination proxy" handling HTTPS for you on top, this will depend on how you deploy your application, your provider might do this for you, or you might need to set it up yourself.

/// tip