Skip to content
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

Unsupported combination of django-proxy and Django #35

Open
JeltevanBoheemen opened this issue May 19, 2022 · 1 comment · May be fixed by #58
Open

Unsupported combination of django-proxy and Django #35

JeltevanBoheemen opened this issue May 19, 2022 · 1 comment · May be fixed by #58
Assignees
Labels
bug Something isn't working

Comments

@JeltevanBoheemen
Copy link
Contributor

django-revproxy supports Django<3.2. See jazzband/django-revproxy#144. The cookiecutter webapp requires Django>4,<5.
This leads to

'HttpResponse' object has no attribute '_headers'

for any url besides /api or /admin. An unreleased version for revproxy (probably) fixes this for Django 4.

Related to https://github.com/UUDigitalHumanitieslab/escaperoom/issues/39

@jgonggrijp jgonggrijp added the bug Something isn't working label May 19, 2022
@ar-jan
Copy link
Contributor

ar-jan commented Oct 19, 2023

django-revproxy==0.11.0 was released, but consensus in https://github.com/UUDigitalHumanitieslab/escaperoom/issues/39 seemed to be that we should also revise the proxying setup.

@jgonggrijp jgonggrijp linked a pull request Nov 5, 2024 that will close this issue
@jgonggrijp jgonggrijp self-assigned this Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants