.Builder()
        .add("*.example.com", certA1Sha256Pin)
        .add("a.example.com", certB1Sha256Pin)
        .add("b.example.com", certC1Sha256Pin)
        .build()

    val expectedPins =
      listOf(
        Pin("*.example.com", certA1Sha256Pin),
        Pin("a.example.com", certB1Sha256Pin),
      )
    assertThat(certificatePinner.findMatchingPins("a.example.com")).isEqualTo(expectedPins)
  }

  @Test

The extractor should handle:

- YAML front matter extraction
- Heading structure
- **Bold text** and *italic text*
- Lists and other formatting

### Code Examples

Here is some inline `code` and a code block:

```java
public class Example {
    public static void main(String[] args) {
        System.out.println("Hello, World!");
    }
}
```

## Links

        CloseableUtil.closeQuietly(in);

        final String content = extractData.getContent();

        // Code blocks should be converted to plain text
        assertTrue(content.contains("public class Example") || content.contains("Example"));
    }

```

With a server that holds a certificate and a client that trusts it we have enough for an HTTPS
handshake. The best part of this example is that we don't need to make our test code insecure with a
a fake `HostnameVerifier` or `X509TrustManager`.

Certificate Authorities
-----------------------

The above example uses a self-signed certificate. This is convenient for testing but not

 * flags is necessary to distinguish which type of Named Pipe behavior
 * is desired.
 *
 * <table border="1">
 * <caption>SmbNamedPipe Constructor Examples</caption>
 * <tr >
 * <td colspan="2"><b><code>SmbNamedPipe</code> Constructor Examples</b></td>
 * <tr>
 * <td ><b>Code Sample</b></td>
 * <td><b>Description</b></td>
 * </tr>
 * <tr>
 * <td >
 *
 * <pre>

 * flags is necessary to distinguish which type of Named Pipe behavior
 * is desired.
 *
 * <table border="1">
 * <caption>SmbNamedPipe Constructor Examples</caption>
 * <tr>
 * <td colspan="2"><b><code>SmbNamedPipe</code> Constructor Examples</b></td>
 * <tr><td ><b>Code Sample</b></td><td><b>Description</b></td></tr>
 * <tr><td ><pre>
 * new SmbNamedPipe( "smb1://server/IPC$/PIPE/foo",

    }

    public void test_match_both() {
        urlFilter.addInclude("http://example.com/.*");
        urlFilter.addExclude("http://example.com/a.*");

        final String sessionId = "id1";
        urlFilter.init(sessionId);

        assertTrue(urlFilter.match("http://example.com/"));
        assertFalse(urlFilter.match("http://example.com/a"));
        assertFalse(urlFilter.match("http://test.com/"));

 * also be resolved to yield the name of the associated Windows account
 * such as <code>Administrators</code> or <code>MYDOM\alice</code>.
 * <p>
 * Consider the following output of <code>examples/SidLookup.java</code>:
 *
 * <pre>
 *        toString: S-1-5-21-4133388617-793952518-2001621813-512
 * toDisplayString: WNET\Domain Admins
 *         getType: 2
 *     getTypeText: Domain group

 * more ACEs are evaluated until all desired access bits (combined)
 * are "allowed". If all of the desired access bits are not "allowed"
 * the then same process is repeated for inherited ACEs.
 * <p>
 * For example, if user <code>WNET\alice</code> tries to open a file
 * with desired access bits <code>0x00000003</code> (<code>FILE_READ_DATA |
 * FILE_WRITE_DATA</code>) and the target file has the following security
 * descriptor ACEs:
 *

        ResponseData responseData1 = new ResponseData();
        responseData1.setUrl("https://example.com/page1");

        ResponseData responseData2 = new ResponseData();
        responseData2.setUrl("https://example.com/page2");

        ResponseData responseData3 = new ResponseData();
        responseData3.setUrl("https://example.com/page3");

        // Execute multiple times - should not throw any exception