Then, when you type that username and password, the browser sends them in the header automatically.

## Simple HTTP Basic Auth { #simple-http-basic-auth }

* Import `HTTPBasic` and `HTTPBasicCredentials`.
* Create a "`security` scheme" using `HTTPBasic`.
* Use that `security` with a dependency in your *path operation*.
* It returns an object of type `HTTPBasicCredentials`:
    * It contains the `username` and `password` sent.

// Should only be called if a failure occurred.
func (o listPathOptions) checkMetacacheState(ctx context.Context, rpc *peerRESTClient) error {
	// We operate on a copy...
	o.Create = false
	c, err := rpc.GetMetacacheListing(ctx, o)
	if err != nil {
		return err
	}
	cache := *c

	if cache.status == scanStateNone || cache.fileNotFound {
		return errFileNotFound
	}

		respRecorder := xhttp.NewResponseRecorder(w)

		// Setup a http request body recorder
		reqRecorder := &xhttp.RequestRecorder{Reader: r.Body}
		r.Body = reqRecorder

		// Create tracing data structure and associate it to the request context
		tc := mcontext.TraceCtxt{
			AmzReqID:         w.Header().Get(xhttp.AmzRequestID),
			RequestRecorder:  reqRecorder,
			ResponseRecorder: respRecorder,
		}

        assertEquals(tree, unwrapped);
        // Test unwrapping to a non-assignable type should fail
        assertThrows(ClassCastException.class, () -> {
            // Create a mock class that extends SmbTree but is not assignable from SmbTreeImpl
            class CustomSmbTree extends SmbTreeImpl {
                CustomSmbTree() {
                    super(session, "SHARE", "A:");
                }

 *   <li>file system errors: permissions</li>
 * </ul>
 *
 * TODO carlos: all these possible has*Exceptions and get*Exceptions methods make the clients too
 *       complex requiring a long list of checks, need to create a parent/interface/encapsulation
 *       for the types of exceptions
 */
@Deprecated
public class ArtifactResolutionResult {
    private static final String LS = System.lineSeparator();

/**
 * Service for creating {@link PathMatcher} objects that can be used to filter files
 * based on include/exclude patterns. This service provides a clean API for plugins
 * to create path matchers without directly depending on implementation classes.
 * <p>
 * The path matchers created by this service support Maven's traditional include/exclude
 * pattern syntax, which is compatible with the behavior of Maven 3 plugins like

        char[] diffAtMiddle = "supersecretpXssword123456789".toCharArray();
        char[] diffAtEnd = "supersecretpassword12345678X".toCharArray();

        // Create authenticators
        NtlmPasswordAuthenticator baseAuth = new NtlmPasswordAuthenticator("domain", "user", new String(basePassword));

    }

    /**
     * Test complete workflow
     */
    public void test_completeWorkflow() {
        // Create transformer with name
        TestTransformer transformer = new TestTransformer();
        transformer.setName("workflowTransformer");

        // Create custom result data
        ResultData customResult = new ResultData();
        customResult.setTransformerName("customName");

            throw new CrawlerSystemException("Unchecked");
        }
    }

    /**
     * Test suppressed exceptions
     */
    public void test_suppressedExceptions() throws Exception {
        // Create exception with suppression enabled
        Constructor<CrawlerSystemException> constructor =
                CrawlerSystemException.class.getDeclaredConstructor(String.class, boolean.class, boolean.class);

import java.util.Deque;

/**
 * Utility class for disposing of resources at the end of an application.
 * <p>
 * If there are resources that must be disposed of at the end of the application,
 * create a class that implements {@link Disposable} and register it with this class.
 * </p>
 *
 * @author koichik
 */
public abstract class DisposableUtil {

    /**
     * Do not instantiate.
     */