A #SoupAuthDomain manages authentication for all or part of a
class@Server. To make a server require authentication, first create
an appropriate subclass of #SoupAuthDomain, and then add it to the
server with soup.server.Server.addAuthDomain.
In order for an auth domain to have any effect, you must add one or more
paths to it (via soup.auth_domain.AuthDomain.addPath). To require authentication for
all ordinary requests, add the path "/". (Note that this does not include
the special "*" URI (eg, "OPTIONS *"), which must be added as a separate
path if you want to cover it.)
If you need greater control over which requests should and shouldn't be
authenticated, add paths covering everything you *might* want authenticated,
and then use a filter (soup.auth_domain.AuthDomain.setFilter to bypass
authentication for those requests that don't need it.
Server-side authentication.
A #SoupAuthDomain manages authentication for all or part of a class@Server. To make a server require authentication, first create an appropriate subclass of #SoupAuthDomain, and then add it to the server with soup.server.Server.addAuthDomain.
In order for an auth domain to have any effect, you must add one or more paths to it (via soup.auth_domain.AuthDomain.addPath). To require authentication for all ordinary requests, add the path "/". (Note that this does not include the special "*" URI (eg, "OPTIONS *"), which must be added as a separate path if you want to cover it.)
If you need greater control over which requests should and shouldn't be authenticated, add paths covering everything you *might* want authenticated, and then use a filter (soup.auth_domain.AuthDomain.setFilter to bypass authentication for those requests that don't need it.