// Process
}  // Temp files auto-deleted
```

---

## Best Practices for AI Assistants

### When Adding Features

1. Read existing code first (use symbol overview tools)
2. Follow existing patterns
3. Add tests
4. Handle resources properly (try-with-resources)
5. Consider thread safety
6. Update JavaDoc

### When Fixing Bugs

1. Write failing test first
2. Understand root cause

     * It should just delegate to the static authenticate method.
     * @throws IOException
     */
    @Test
    public void testDoAuthentication() throws IOException {
        // Setup: No "Authorization" header to follow a simple path
        when(mockRequest.getHeader("Authorization")).thenReturn(null);

        // Execute

 * resources are files and directories however an <code>SmbFile</code>
 * may also refer to servers and workgroups. If the resource is a file or
 * directory the methods of <code>SmbFile</code> follow the behavior of
 * the well known {@link java.io.File} class. One fundamental difference
 * is the usage of a URL scheme [1] to specify the target file or
 * directory. SmbFile URLs have the following syntax:
 *

 */

package jcifs.smb1.smb1;

/**
 * Interface defining NT status codes used in SMB1 protocol operations.
 * These status codes are returned by SMB servers to indicate the result
 * of requested operations. The codes follow the Windows NT status code format.
 */
public interface NtStatus {

    /* Don't bother to edit this. Everthing within the interface
     * block is automatically generated from the ntstatus package.
     */

|-------------|----------------|
| Collection | WebConfig or FileConfig |
| Start URLs | URLs field in crawl config |
| Good URL Pattern | Included URLs (regex) |
| Bad URL Pattern | Excluded URLs (regex) |
| Follow/Index Pattern | Config Depth and Filter settings |

**Implementation Details**

See the GSA parser implementation: [GsaConfigParser.java](/src/main/java/org/codelibs/fess/util/GsaConfigParser.java)

 * resources are files and directories however an <code>SmbFile</code>
 * may also refer to servers and workgroups. If the resource is a file or
 * directory the methods of <code>SmbFile</code> follow the behavior of
 * the well known {@link java.io.File} class. One fundamental difference
 * is the usage of a URL scheme [1] to specify the target file or
 * directory. SmbFile URLs have the following syntax:
 *

linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.

  The precise terms and conditions for copying, distribution and
modification follow.  Pay close attention to the difference between a
"work based on the library" and a "work that uses the library".  The
former contains code derived from the library, whereas the latter must