Google Cloud App Engine灵活环境：Flask应用配置HTTPS问题求助

Let's break down why you're seeing this error and how to fix it, whether you're testing locally or deploying to Google Cloud:

1. Why the Error Happens #

Talisman's default behavior is to force HTTPS redirects, but when running Flask locally without an SSL certificate, there's no valid HTTPS server to redirect to. Even with debug=False, Flask still doesn't serve HTTPS out of the box—so the browser gets an invalid response because it expects a secure connection but doesn't receive one.

2. Solution 1: Disable HTTPS Enforcement for Local Development #

Since you don't need HTTPS for local testing (unless you're debugging OAuth flows that require it), you can conditionally turn off Talisman's force_https setting based on your environment. Here's how:

from flask import Flask
from flask_talisman import Talisman
import os

app = Flask(__name__)

# Only enforce HTTPS in production (GCP)
is_production = os.getenv('FLASK_ENV') == 'production' or not app.debug
Talisman(app, force_https=is_production)

# Your routes and application logic here...

This way, local development uses HTTP (no redirects, no errors), while your GCP deployment will automatically force HTTPS as intended.

3. Solution 2: Use a Self-Signed Certificate for Local HTTPS Testing #

If you need to test HTTPS locally (e.g., for OAuth callbacks that require secure URLs), generate a self-signed SSL certificate and configure Flask to use it:

Step 1: Generate the Certificate #

Run this OpenSSL command in your terminal to create a certificate and key file:

openssl req -x509 -newkey rsa:4096 -nodes -out cert.pem -keyout key.pem -days 365

You can fill in the prompts with dummy values—this is just for local testing.

Step 2: Run Flask with SSL #

Update your app's entry point to use the certificate:

if __name__ == '__main__':
    app.run(ssl_context=('cert.pem', 'key.pem'), debug=False)

Or run Flask via the command line:

flask run --ssl-cert=cert.pem --ssl-key=key.pem

When you visit https://127.0.0.1:5000, your browser will warn you about an untrusted certificate—this is normal for self-signed certs. Click "Advanced" > "Proceed to 127.0.0.1" to access the secure local server, and Talisman will work without errors.

4. GCP Production Environment Notes #

Good news: You don't need to handle SSL certificates manually on Google Cloud. Services like App Engine, Cloud Run, or GKE with Load Balancing automatically provide managed SSL certificates and handle HTTPS termination. Your Flask app can still serve HTTP internally—GCP will handle converting external HTTPS requests to HTTP for your app.

Just make sure Talisman's force_https is enabled (which it is by default when not in debug mode), and GCP will take care of the rest. Users will only be able to access your app via HTTPS, which is exactly what you want.

内容的提问来源于stack exchange，提问作者Arhire Ionut