hazza/jupyterhub
1
0
Fork 0
mirror of https://github.com/jupyterhub/jupyterhub.git synced 2025-10-07 10:04:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #4932 from manics/subdowmain-doc

Browse Source 
Remove out-of-date info from subdomain_hook doc
This commit is contained in:
Min RK
2024-10-20 09:14:56 +02:00
committed by GitHub
parent f2ecf6a307 e4ae7ce4fe
commit 1cb98ce9ff
1 changed files with 1 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
jupyterhub/app.py
View File

@@ -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.