> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/operations/https.md). # HTTPS HTTPS is a protocol for secure communications over a computer network that is used to access the Internet. HTTPS consists of communications over Hypertext Transfer Protocol (HTTP) within a connection that is encrypted by Transport Layer Security. HTTPS is used to provide authentication of a website as well as bidirectional encryption of the communications between the client and server. ### TelcoBridges and HTTPS The TelcoBridges [Web Portal](/tmedia-documentation/other-pages/other/web-portal.md) can be configured to support HTTPS; however, only the encryption functionality is used. This is because the web server hosting the Web Portal does not authenticate itself. Note that the recovery web portal will use HTTP (when using "[reset host role](/tmedia-documentation/configuration/web-portal-3-3/system/host-role/reset-hostrole.md)" or "change network devices roles"). ### Configuration * [Toolpack v3.0: HTTPS](/tmedia-documentation/other-pages/system-settings-overview/tmedia-tdev-and-tsig-web-portal-3-0-system-settings.md#services) ### References * [Wikipedia article](https://en.wikipedia.org/wiki/HTTPS) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/operations/https.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.