From e4ae7ce4fe4e3b5d21d1cd23550a22a7efa2aba7 Mon Sep 17 00:00:00 2001 From: Simon Li Date: Sun, 20 Oct 2024 00:11:27 +0100 Subject: [PATCH] Remove out-of-date info from subdomain_hook doc --- jupyterhub/app.py | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/jupyterhub/app.py b/jupyterhub/app.py index c7b4770a..06830951 100644 --- a/jupyterhub/app.py +++ b/jupyterhub/app.py @@ -873,13 +873,7 @@ class JupyterHub(Application): but your identity provider is likely much more strict, allowing you to make assumptions about the name. - The default behavior is to have all services - on a single `services.{domain}` subdomain, - and each user on `{username}.{domain}`. - This is the 'legacy' scheme, - and doesn't work for all usernames. - - The 'idna' scheme is a new scheme that should produce a valid domain name for any user, + The 'idna' hook should produce a valid domain name for any user, using IDNA encoding for unicode usernames, and a truncate-and-hash approach for any usernames that can't be easily encoded into a domain component.