> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/monitors/cloud-and-infrastructure-monitoring/gcp/how-to-resolve-sprinto-check-to-redirect-traffic-from-http-to-https-for-google-cloud-platform-gcp.md).

# How to resolve Sprinto check to redirect traffic from http to https for Google Cloud Platform (GCP)

### About

The above Sprinto check starts failing if no HTTP header is created on your integrated GCP account to redirect the traffic to the HTTPS protocol.

### Purpose

Redirecting HTTP requests to HTTPS on the GCP account enhances data security by ensuring all data transmitted between clients and the server is encrypted. This prevents unauthorized access and eavesdropping on sensitive information, such as login credentials and personal data. By enforcing HTTPS, you protect data integrity and confidentiality, ensuring secure communication and compliance with security standards and regulations.

### Redirecting Requests from HTTP to HTTPS on GCP

#### Before you begin

* Make sure you have the administrator privilege on the GCP account to modify the GCP configuration.
* Ensure that you have the HTTPS load balancer (LB1) created and in the working status.

#### Procedure

You need to create an HTTP load balancer (LB2) to redirect HTTP traffic to the HTTPS protocol. Refer to the [Google documentation](https://cloud.google.com/load-balancing/docs/https/setting-up-http-https-redirect#partial-http-lb) to redirect the traffic.

Upon completing the above configuration, Sprinto sets the check’s status to “Passing.”

Please contact [Sprinto Support](mailto:www.support@sprinto.com) if you have any queries related to the check or need any assistance.


---

# 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://docs.sprinto.com/monitors/cloud-and-infrastructure-monitoring/gcp/how-to-resolve-sprinto-check-to-redirect-traffic-from-http-to-https-for-google-cloud-platform-gcp.md?ask=<question>&goal=<user_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.
