Pull request #1402 changes the redirect handling in werkzeug.test.Client and seems to reuse the environ from the first request to follow the redirect. This leads to problems when the application modifies the environ in-place.
I have a multi-tenant application which resolves the tenant from the first path element in a middleware with werkzeug.wsgi.pop_path_info() before passing the request to a Flask application. This behavior is recommended by the Flask documentation: http://flask.pocoo.org/docs/0.12/patterns/appdispatch/#dispatch-by-path
However, combining pop_path_info() and redirects will breaks tests with Werkzeug >= 0.15 because when Werkzeug makes the second request following the redirct, it will reuse an environ where the first path element is already gone.
Here is a test application which demonstrates this problem:
from flask import Flask, redirect, url_for
from werkzeug.test import Client
from werkzeug.wrappers import BaseResponse
from werkzeug.wsgi import pop_path_info
app = Flask(__name__)
@app.route("/first")
def first():
return redirect(url_for('.second'))
@app.route("/second")
def second():
return b'hello'
client = Client(app, BaseResponse)
r = client.get('/first', follow_redirects=True)
assert r.data == b'hello'
def middleware(environ, start_response):
print('Before pop_path_info(): %s' % environ['PATH_INFO'])
pop_path_info(environ)
print('After pop_path_info(): %s' % environ['PATH_INFO'])
return app(environ, start_response)
client = Client(middleware, BaseResponse)
r = client.get('/tenant/first', follow_redirects=True)
assert r.data == b'hello'
Pull request #1402 changes the redirect handling in werkzeug.test.Client and seems to reuse the
environfrom the first request to follow the redirect. This leads to problems when the application modifies theenvironin-place.I have a multi-tenant application which resolves the tenant from the first path element in a middleware with
werkzeug.wsgi.pop_path_info()before passing the request to a Flask application. This behavior is recommended by the Flask documentation: http://flask.pocoo.org/docs/0.12/patterns/appdispatch/#dispatch-by-pathHowever, combining
pop_path_info()and redirects will breaks tests with Werkzeug >= 0.15 because when Werkzeug makes the second request following the redirct, it will reuse anenvironwhere the first path element is already gone.Here is a test application which demonstrates this problem: