This commit introduced a breaking change where the next_path is now being encoded. That's an issue if your next_path is a full URL since the schema will be encoded (https:// -> https%3A//) resulting in an error on redirect.
Can that change be reverted?