* and {@link UrlQueue}. It also uses {@link CrawlingParameterUtil} to access services
 * like {@link UrlQueueService} and DataService, as well as the {@link CrawlerContext}.
 * </p>
 *
 * <p>
 * The class provides methods to check if a response is successful or not modified based on
 * configured HTTP status codes. It also handles the storage of child URLs found in the
 * response data, respecting the maximum depth and access count limits.

/**
 * Represents the response data obtained from a crawled resource.
 * This class encapsulates various details of an HTTP response, including
 * status code, content type, content length, and the response body.
 * It also provides methods for managing metadata, child URLs, and temporary files.
 */
public class ResponseData implements Closeable {

    private String url;

    private int httpStatusCode;

    private String charSet;

            throw e;
        }
    }

    /**
     * FtpInfo is a helper class that encapsulates information about an FTP URL.
     * It parses the URL and provides methods to retrieve the host, port, parent directory,
     * and file name. It also provides methods to construct URLs for child paths.
     *
     * <p>
     * Usage example:
     * </p>
     *
     * <pre>
     * {@code

 * This client supports authentication, content retrieval, and metadata extraction from SMB files.
 * It handles file access, directory listing, and access control entries (ACEs) processing.
 * </p>
 *
 * <p>
 * The class provides methods to:
 * </p>
 * <ul>
 *   <li>Initialize the client with SMB authentication details.</li>
 *   <li>Retrieve content and metadata from SMB files.</li>

 *   <li>Extracting child URLs from the HTML content based on configured rules.</li>
 *   <li>Handling redirect URLs specified in the response headers.</li>
 * </ol>
 * <p>
 * The class also provides methods for configuring features and properties of the
 * underlying DOM parser, as well as defining rules for extracting child URLs
 * from specific HTML tags and attributes.
 * </p>
 *
 * <p>
 * <b>Configuration:</b>

     the things they contain, so they don't accidently get detected
     as what's in them
   * For logic too complex to be expressed in a magic match, do the best
     you can here, then provide a Custom Detector for the rest
-->
<mime-info xmlns:tika="https://tika.apache.org/">

  <mime-type type="application/activemessage"/>
  <mime-type type="application/andrew-inset">
    <glob pattern="*.ez"/>