BasicHttp/WsHttp Binding
- Last UpdatedJun 03, 2026
- 1 minute read
For these bindings, URL access must be registered using the netsh command. This applies to all accounts, including built-in Windows service accounts.
Command format
netsh http add urlacl url={UriScheme}://+:{port}/{Project-GUID}/GlobalWcfServiceLib/GlobalWcfService_11_1_201011/ user=Domain\Username
-
For UriScheme, enter http or https, depending on the protocol. If both are used, run the command once for each.
-
For Project GUID, enter A GUID unique to each project, included in the demon URL.
Note: To avoid registering each project separately, register the URL prefix. However, this grants access to all HTTP endpoints matching the scheme and port, including other services, so use it cautiously.
netsh http add urlacl url={UriScheme}://+:{port}/
Note: Wildcards cannot be used for ports or URL segments. If multiple ports are needed, run the command separately for each.
Examples
Grant access to Network Service for a specific project (HTTP):
netsh http add urlacl url=http://+:8000/d29a149a-b6ce-4d4e-972a-38fff0ca7015/GlobalWcfServiceLib/GlobalWcfService_11_1_201011/ user="NT AUTHORITY\NetworkService"
Grant access to Network Service with a wildcard prefix (HTTP):
netsh http add urlacl url=http://+:8000/ user="NT AUTHORITY\NetworkService"
Grant access to a domain user for a specific project (HTTPS):
netsh http add urlacl url=https://+:8000/d29a149a-b6ce-4d4e-972a-38fff0ca7015/Global
Revoke User Permissions
-
List all URL registrations by running:
netsh http show urlacl
-
Locate the URL registration granting access to the account, copy the URL, and replace it in the following command:
netsh http delete urlacl url={url}