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

Deprecate WSGIMiddleware in favor of a2wsgi #1503

Closed
2 tasks done
Kludex opened this issue Feb 10, 2022 · 0 comments · Fixed by #1504
Closed
2 tasks done

Deprecate WSGIMiddleware in favor of a2wsgi #1503

Kludex opened this issue Feb 10, 2022 · 0 comments · Fixed by #1504
Labels
clean up Refinement to existing functionality documentation Project documentation

Comments

@Kludex
Copy link
Member

Kludex commented Feb 10, 2022

Checklist

  • There are no similar issues or pull requests for this yet.
  • I discussed this idea on the community chat and feedback is positive.

Is your feature related to a problem? Please describe.

I want to deprecate WSGIMiddleware and recommend a2wsgi on the documentation.

Right now, the WSGIMiddleware is not documented, so not that harmful to deprecate. I expect the deprecation message to inform about a2wsgi or recommend the specific page on the docs so users using the middleware can fix the warning easily.

Describe the solution you would like.

No response

Describe alternatives you considered

No response

Additional context

Gitter conversation about the topic:

image

@Kludex Kludex added clean up Refinement to existing functionality documentation Project documentation labels Feb 10, 2022
@Kludex Kludex changed the title Deprecate WSGIMiddleware Deprecate WSGIMiddleware in favor of a2wsgi Feb 10, 2022
@Kludex Kludex changed the title Deprecate WSGIMiddleware in favor of a2wsgi Deprecate WSGIMiddleware in favor of a2wsgi Feb 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clean up Refinement to existing functionality documentation Project documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant