Matthias Kestenholz

@leiserfg That exists already in the form of the `pathsend` extension: https://asgi.readthedocs.io/en/latest/extensions.html#path-send

Thanks for your report! If the environment is completely air-gapped (and therefore untrusted outsiders cannot ever access it) can't you add the known IP addresses of people accessing the service...

You should be able to solve this by using something like: ```python # Don't use this in production environments accessible to the internet DEBUG_TOOLBAR_CONFIG = {"SHOW_TOOLBAR_CONFIG": lambda request: DEBUG and...

Oh, yes. Sorry for that.

Good to hear! I added the documentation label because we should probably re-check the documentation and mention this somewhere. Additionally, I am getting the impression that asking the DNS resolver...

@tim-schilling How would such an opt-in check work? Using a setting? I think I was sceptical about the autoconfiguration at the start, but something like #2118 seems like a good...

As discussed on the djangonauts call: We are currently impacting people negatively who aren't using Docker at all and we shouldn't do that. The way to go would be to...

I worry a bit about keeping other language versions current, but that shouldn't stop anyone from contributing docs in additional languages. Maybe it would be useful to have other languages...

> I suggested some changes. Also, there was a concern that it may be a valid use case to allow for a subset of settings to be excluded from the...

A first change has already landed addressing this but isn't yet a part of a release. `INTERNAL_IPS` is now checked before trying to resolve `host.docker.internal` and that should hopefully fix...