Python 通过gunicorn和nginx使用flask googlelogin导致400个错误请求
更新:当我将我的nginx服务器配置为允许http并将googleoauth的重定向URI设置为使用http(而不是https)时,它似乎可以工作。我真的更喜欢使用HTTPS,所以任何想法都很感激Python 通过gunicorn和nginx使用flask googlelogin导致400个错误请求,python,nginx,flask,google-oauth,Python,Nginx,Flask,Google Oauth,更新:当我将我的nginx服务器配置为允许http并将googleoauth的重定向URI设置为使用http(而不是https)时,它似乎可以工作。我真的更喜欢使用HTTPS,所以任何想法都很感激 我正在尝试使用flask googlelogin插件授权用户访问我的web应用程序。当运行调试服务器并直接连接到它时,一切正常,但当我在nginx后面运行我的应用程序作为反向代理时(无论是到调试服务器还是到运行在gunicorn内部的应用程序),我的登录回调上会收到400个错误请求响应,上面写着“浏
我正在尝试使用flask googlelogin插件授权用户访问我的web应用程序。当运行调试服务器并直接连接到它时,一切正常,但当我在nginx后面运行我的应用程序作为反向代理时(无论是到调试服务器还是到运行在gunicorn内部的应用程序),我的登录回调上会收到
400个错误请求
响应,上面写着“浏览器(或代理)”发送了此服务器无法理解的请求”
gunicorn日志(使用gunicorn运行时)没有显示任何有趣的内容。nginx日志(在info
级别)显示返回的400:
» tail -f /var/log/nginx/*
==> /var/log/nginx/access.log <==
76.164.174.115 - - [21/May/2014:13:07:46 -0500] "GET /login HTTP/1.1" 200 1368 "-" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.131 Safari/537.36"
76.164.174.115 - - [21/May/2014:13:07:49 -0500] "GET /oauth2callback?state=[redacted]&code=[redacted] HTTP/1.1" 400 192 "https://redacted.com/login" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.131 Safari/537.36"
因此GET被代理给应用程序,但出于某种原因flask不喜欢它。以下是我申请的相关部分:
from flask import Flask, request, render_template, redirect, url_for, flash, session
from flask_login import current_user, login_required, login_user, logout_user, UserMixin, LoginManager
from flask_googlelogin import GoogleLogin
from werkzeug.contrib.fixers import ProxyFix
import json
app = Flask(__name__)
app.wsgi_app = ProxyFix(app.wsgi_app)
app.secret_key = "redacted"
app.config.update(
GOOGLE_LOGIN_CLIENT_ID='redacted',
GOOGLE_LOGIN_CLIENT_SECRET='redacted',
GOOGLE_LOGIN_REDIRECT_URI='https://redacted.com/oauth2callback',
)
login_manager = LoginManager()
login_manager.init_app(app)
login_manager.login_view = "login"
login_manager.login_message = u"Please log in to access this page."
login_manager.login_message_category = u"danger"
googlelogin = GoogleLogin(app, login_manager)
class User(UserMixin):
def __init__(self, userinfo):
self.name = userinfo['name']
self.id = userinfo['id']
self.picture = userinfo.get('picture')
users = {
"redacted1" : None,
"redacted2" : None,
}
@googlelogin.user_loader
@login_manager.user_loader
def load_user(userid):
return users.get(userid)
@app.route("/login", methods=['GET', 'POST'])
def login():
return render_template('login.html', login_url=googlelogin.login_url())
@app.route('/oauth2callback')
@googlelogin.oauth2callback
def oauth2callback(token, userinfo, **params):
if userinfo['id'] in users:
user = users[userinfo['id']] = User(userinfo)
login_user(user)
session['token'] = json.dumps(token)
flash("Logged in", "success")
return redirect(params.get('next', url_for('automation')))
else:
flash("That google user is not authorized.", "danger")
return redirect(url_for('login'))
@app.route("/automation", methods=['GET'])
@login_required
def automation():
return render_template('automation.html')
@app.route("/logoff")
@login_required
def logoff():
logout_user()
session.clear()
flash("logged out", "info")
return redirect(url_for('login'))
if __name__ == "__main__":
app.config.update( GOOGLE_LOGIN_REDIRECT_URI='http://localhost:5000/oauth2callback' )
app.run(debug=True)
烧瓶中出现400个错误请求的常见原因似乎是视图函数中未捕获的异常,但我已尝试将整个oauth2callback
缩减为只有print
和pass
的状态,但仍然失败,并且我看不到打印输出
以下是我的nginx配置的相关部分:
server {
listen 443;
server_name redacted.com www.redacted.com;
root /usr/share/nginx/www;
index index.html index.htm;
ssl on;
ssl_certificate /etc/ssl/certs/ssl-bundle.pem;
ssl_certificate_key /etc/ssl/private/myserver.key;
ssl_session_timeout 5m;
ssl_protocols SSLv3 TLSv1;
ssl_ciphers ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv3:+EXP;
ssl_prefer_server_ciphers on;
location / {
try_files $uri $uri/ @proxy_to_app;
}
location @proxy_to_app {
proxy_pass http://127.0.0.1:8000;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
}
提前感谢。我在使用uwsgi时遇到了同样的问题
我可以通过在我的/etc/nginx/uwsgi_参数中添加以下行来修复它
uwsgi_param UWSGI_SCHEME $server_protocol;
我还添加了我的app.config
app.config['GOOGLE_LOGIN_REDIRECT_SCHEME'] = "https"
祝你好运
app.config['GOOGLE_LOGIN_REDIRECT_SCHEME'] = "https"