You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a general inconsistency in "url" vs "urlpath" that makes things harder to understand.
a url is according to scheme:[//[user:password@]host[:port]][/]path[?query][#fragment], meaning that http://host:8000/foo/bar is a url. /foo/bar is not.
a urlpath is a path that goes into a url. We want this distinction because some paths are on the physical machine instead, so just saying path does not convey the appropriate context.
This inconsistency is inherited from jupyterhub, but now that we have control of the spawner and we pass what we want at the command line, we should be clear on the intent to avoid confusion.
The text was updated successfully, but these errors were encountered:
There's a general inconsistency in "url" vs "urlpath" that makes things harder to understand.
scheme:[//[user:password@]host[:port]][/]path[?query][#fragment]
, meaning thathttp://host:8000/foo/bar
is a url./foo/bar
is not.This inconsistency is inherited from jupyterhub, but now that we have control of the spawner and we pass what we want at the command line, we should be clear on the intent to avoid confusion.
The text was updated successfully, but these errors were encountered: