Special names "-"and "-.-", when it is used in the "host:port" part of URL, means the host and port of the DeleGate itself. And URL "http://-.-/-/" is reserved for a entry point of a control page of DeleGate.

Another reserved name is "mypro.xyz". An access to "http://mypro.xyz" is interpreted to your proxy server like "http://-.-". If the proxy is chained, you can access to upstream proxies by prefixing the hop count N from your client, as "http://N.mypro.xyz", as "http://2.mypro.xyz" for example. This feature can be enabled or disabled by the HTTPCONF=mypro.xyz parameter.

This list is passed in to Chrome using a comma-separated list of URLs to Chrome via the "auth-server-whitelist" command-line switch.  For example, you can pass in:

--auth-server-whitelist="*example.com,*foobar.com,*baz"

which would tell chrome that any URL ending in either 'example.com', 'foobar.com' or 'baz' is in the permitted list.  Without the '*' prefix, the URL has to match exactly.

LDH names: Textual representations of DNS names where the

labels of the domain are all "letters, digits,

hyphen" labels as described by [RFC5890]. Trailing

periods are optional.

Domain Name: The label assigned to a node in the Domain Name System.

Names in the user namespace consist of a UTF-8 string tag followed by

"@" followed by a DNS domain name. Note that the tag MUST NOT

contain an "@" character. For example, the "sample" tag used by

Example Corporation could be "sample@example.com".

However, many Unicast DNS implementers have read these RFCs

differently, and argue that the 255-byte limit does include the

terminating zero, and that the "Clarifications to the DNS

Specification" [RFC2181] statement that "." is the "zero length full

name" was simply a mistake.

Hence, implementers should be aware that other Unicast DNS

implementations may limit the maximum domain name to 254 bytes plus a

terminating zero, depending on how that implementer interpreted the

DNS specifications.

Compliant Multicast DNS implementations MUST support names up to 255

bytes plus a terminating zero, i.e., 256 bytes total.

Note that .onion names are required to conform with DNS name syntax

(as defined in Section 3.5 of [RFC1034] and Section 2.1 of

[RFC1123]), as they will still be exposed to DNS implementations.

The BNF of the realm portion allows the realm to begin with a digit,

which is not permitted by the BNF described in [RFC1035]. This

change was made to reflect current practice; although not permitted

by the BNF described in [RFC1035], Fully Qualified Domain Names

(FQDNs) such as 3com.com are commonly used and accepted by current

software.

Domain name: Section 3.1 of [RFC1034] talks of "the domain name

space" as a tree structure. "Each node has a label, which is zero

to 63 octets in length. ... The domain name of a node is the list

of the labels on the path from the node to the root of the tree.

... To simplify implementations, the total number of octets that

represent a domain name (i.e., the sum of all label octets and

label lengths) is limited to 255." Any label in a domain name can

contain any octet value.

The Exceptions box allows you to specify what hostnames are configured to bypass the proxy. Beyond hostnames, it supports two special tokens:

<local> – Matches “plain” hostnames (with no embedded dots)

<-loopback> – Unmatches localhost, 127.0.0.1 and other “loopback” addresses.

WinINET defaults to automatically bypassing the proxy for loopback addresses; this token disables that behavior.

This token impacts WinINET and current versions of WinHTTP; the .NET Framework simply ignores it.

The return value of NPP_GetSitesWithData and the 'site' argument to NPP_ClearSiteData must be domains only (not complete URIs or IRIs). For ASCII domains, they must be lowercase; in the case of internationalized domains, they must be NFKC-encoded (normalized) UTF-8. No other encoding is allowed. IP address literals must be enclosed in square brackets '[]'. This is in accordance with RFC 3987, Internationalized Resource Identifiers (IRIs).