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.

Sign up for GitHub

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

Jump to bottom

Resolve deprecation of `django.utils.http.is_safe_url` in Django 3.0 #72

Merged

browniebroke merged 1 commit into master from feature/is-safe-url

Jun 2, 2020

Owner

browniebroke commented Jun 2, 2020

From Django 3.0 release notes:

To avoid possible confusion as to effective scope, the private internal utility is_safe_url() is renamed to url_has_allowed_host_and_scheme(). That a URL has an allowed host and scheme doesn’t in general imply that it’s “safe”. It may still be quoted incorrectly, for example. Ensure to also use iri_to_uri() on the path component of untrusted URLs.


          New transformers to resolve deprecations of `django.utils.http.is_saf…

cddad75

…e_url` in Django 3.0

browniebroke added the enhancement label

browniebroke merged commit 4b39dd4 into master

browniebroke deleted the feature/is-safe-url branch

June 2, 2020 21:51

browniebroke added this to the Django 4.0 milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels