AuthDomain
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 method@Server.add_auth_domain.
In order for an auth domain to have any effect, you must add one or more paths to it (via method@AuthDomain.add_path). 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 (method@AuthDomain.set_filter to bypass authentication for those requests that don't need it.
Skipped during bindings generation
method
filter
: Property has no gettermethod
filter-data
: Property has no getter nor settermethod
generic-auth-callback
: Property has no gettermethod
generic-auth-data
: Property has no getter nor settermethod
proxy
: Property has no getter nor setter
Inheritors
Constructors
Functions
Checks if @msg contains appropriate authorization for @domain to accept it.
Adds a "WWW-Authenticate" or "Proxy-Authenticate" header to @msg.
Checks if @msg authenticates to @domain via @username and
Checks if @domain requires @msg to be authenticated (according to its paths and filter function).
Removes @path from @domain.
Adds @filter as an authentication filter to @domain.
Sets @auth_callback as an authentication-handling callback for @domain.