val cookieManager = CookieManager(null, CookiePolicy.ACCEPT_ORIGINAL_SERVER)
    val cookieA = HttpCookie("a", "android")
    cookieA.domain = serverUrl.host
    cookieA.path = "/"
    cookieManager.cookieStore.add(serverUrl.toUri(), cookieA)
    val cookieB = HttpCookie("b", "banana")
    cookieB.domain = serverUrl.host
    cookieB.path = "/"
    cookieManager.cookieStore.add(serverUrl.toUri(), cookieB)
    client =

     * 
     * @param fqdn
     */
    void fixupHost ( String fqdn );


    /**
     * Possibly appends the given domain name to the host name if it is currently unqualified
     * 
     * @param domain
     */
    void fixupDomain ( String domain );


    /**
     * Reduces path consumed by the given value
     * 
     * @param i
     */
    void stripPathConsumed ( int i );

		<Property name="searchlog.log.pattern" value="%msg%n" />
	</Properties>

	<Appenders>
		<RollingFile name="AppFile" fileName="${log.file.basedir}/${domain.name}.log"
			filePattern="${log.file.basedir}/${domain.name}${backup.date.suffix}-%i.log.gz">
			<PatternLayout><Pattern>${log.pattern}</Pattern></PatternLayout><!-- <EcsLayout serviceName="fess" eventDataset="app" /> -->
			<Policies>

            final String domain = paramMap.get(CRAWLER_WEB_AUTH + "." + webAuthName + ".domain");
            credentials = new NTCredentials(username, password == null ? StringUtil.EMPTY : password,
                    workstation == null ? StringUtil.EMPTY : workstation, domain == null ? StringUtil.EMPTY : domain);
        } else {

## Context

Modern best practices when developing a Gradle plugin are to use lazy types (ConfigurableFileCollection, Provider API, domain object containers) when defining configurable parts of a plugin (tasks, extensions, domain objects).  The Provider API provides a consistent way to set conventions, wire related configuration together (extension <- domain object <- task) and avoid evaluation ordering problems.

  <url>http://www.apache.org/</url>
  <scm>
    <connection>scm:my-scm:http://domain.org/base</connection>
    <developerConnection>scm:my-scm:https://domain.org/base/</developerConnection>
    <url>https://domain.org/base</url>
  </scm>
  <distributionManagement>
    <site>
      <url>scp://scp.domain.org/base/</url>
    </site>
  </distributionManagement>

       child.scm.url.inherit.append.path="false">
    <connection>scm:my-scm:http://domain.org/base</connection>
    <developerConnection>scm:my-scm:https://domain.org/base/</developerConnection>
    <url>https://domain.org/base</url>
  </scm>
  <distributionManagement>
    <site child.site.url.inherit.append.path="false">
      <url>scp://scp.domain.org/base/</url>
    </site>
  </distributionManagement>

  <url>http://www.apache.org/path/to/parent/</url>
  <scm>
    <connection>scm:my-scm:http://domain.org/base</connection>
    <developerConnection>scm:my-scm:https://domain.org/base/</developerConnection>
    <url>https://domain.org/base</url>
  </scm>
  <distributionManagement>
    <site>
      <url>scp://scp.domain.org/base/</url>
    </site>
  </distributionManagement>

        "The logon request failed because the trust relationship between the primary domain and the trusted domain failed.",
        "The logon request failed because the trust relationship between this workstation and the primary domain failed.",
        "The account used is a Computer Account. Use your global user account or local user account to access this server.",

 * to protect content with NTLM HTTP Authentication. Servlets that
 * extend this abstract base class may be authenticated against an SMB
 * server or domain controller depending on how the
 * <tt>jcifs.smb.client.domain</tt> or <tt>jcifs.http.domainController</tt>
 * properties are be specified. <b>With later containers the