-
-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AttributeError: 'HttpResponse' object has no attribute '_headers' #126
Comments
This was changed a while ago: django/django@bcc2bef |
Oh. It isn't changed in the version installed though PIP. |
Sorry, I'm agreeing with this issue, and the django change is pretty old. |
Experiencing the same issue here |
Same here. |
* check for `response.headers` attribute, fallback to old interface if missing * updated tests to expect Django 3.2+ response.headers * added Django 3.2 with Python 3.8 job in .travis.yml
* check for `response.headers` attribute, fallback to old interface if missing * updated tests to expect Django 3.2+ response.headers * added Django 3.2 in .travis.yml
* check for `response.headers` attribute, fallback to old interface if missing * updated tests to expect Django 3.2+ response.headers * added Django 3.2 in .travis.yml
Any idea when this will be in master? Everyone who has moved to Django 3.2 will be affected by this. |
add Django 3.2 support (fixes jazzband#126)
Is there an estimate when this will be merged? |
add Django 3.2 support (fixes jazzband#126)
any update or estimate on when this will be available on PyPi? Thanks! |
I think this project is basically dead, sorry. I was working on it a while back, but no longer working on the project or employer that required it. Best bet might be to fork it, change the name, and upload the new name to PyPI. |
@brianmay what about transferring the project to Jazzband? That would make it easier for everyone involved. If you're able, please reach out to @seocam about this. There's quite a community around this project, it would fit nicely in the Jazzband collective in my opinion. If that's off the table for any reason, we will mantain our fork over at https://github.com/Innovativity/django-revproxy for LTS Django releases and we'll provide a new PyPI package to keep the project alive. That would be a backup solution though. |
Who is Jazzband? There have been times abandoned projects get transferred to new maintainers, who then abuse the privilege, and introduce malware into new releases. Which means the project is in even worse state then just being abandoned. Wouldn't want to do that here. Technically this isn't my project, @seocam was maintaining it, until he ran out of time #75 (comment). I was granted full access #75 (comment) to the github project, pypi, and readthedocs (did I miss anything?). Unless anybody raises objections, I think I can make any change in the best interests of this project. If my understanding of Jazzband is correct, it is probably a good home for this project. Although I have no idea what to do with PyPI and readthedocs access, which probably will also be required. |
That's unfortunately very true, and part of the reasoning behind Jazzband
I think, but I may be wrong, only the owner can transfer the repo. That's why I proposed to raise the question to @seocam, sorry it came out that way, I didn't mean to doubt your position!
That's something that should be discussed with them later on I think. Thank you @brianmay for your help with this! |
* check for `response.headers` attribute, fallback to old interface if missing * updated tests to expect Django 3.2+ response.headers * added Django 3.2 in .travis.yml
Hello, any solution for this case? I still have issue with this
|
Same here... |
Please, anyone have solution? |
Same issue |
1 similar comment
Same issue |
Install the master branch should work |
Same issue, some solution? |
@JPereira-FJB |
We are waiting the 0.11.0 release but, in the meantime, you can try this: jazzband/help#330 (comment) |
This statement is producing an error:
logger.debug('Response headers: %s', getattr(response, '_headers'))
In these 2 files:
"...lib64/python3.7/site-packages/revproxy/utils.py", line 127, in set_response_headers
"...lib64/python3.7/site-packages/revproxy/response.py", line 48, in get_django_response
The text was updated successfully, but these errors were encountered: