* <ul>
     *   <li>&amp; with &amp;amp;</li>
     *   <li>&lt; with &amp;lt;</li>
     *   <li>&gt; with &amp;gt;</li>
     *   <li>" with &amp;quot;</li>
     *   <li>' with &amp;apos;</li>
     * </ul>
     * Additionally, it strips invalid XML characters from the input string.
     *
     * @param value the input string to be escaped
     * @return the escaped XML string with invalid characters removed
     */

    /** Array of supported web protocols with colon suffix (e.g., "http:", "https:") */
    protected String[] webProtocols = StringUtil.EMPTY_STRINGS;

    /** Array of supported file protocols with colon suffix (e.g., "file:", "ftp:") */
    protected String[] fileProtocols = StringUtil.EMPTY_STRINGS;

    /**
     * Default constructor for ProtocolHelper.

        run: echo "$GITHUB_CONTEXT"
      - uses: actions/checkout@v5
      - name: Set up Python
        uses: actions/setup-python@v5
        with:
          python-version: "3.11"
      - name: Setup uv
        uses: astral-sh/setup-uv@v6
        with:
          version: "0.4.15"
          enable-cache: true
          cache-dependency-glob: |
            requirements**.txt
            pyproject.toml

```

The TLS versions and cipher suites in each spec can change with each release. For example, in OkHttp 2.2 we dropped support for SSL 3.0 in response to the [POODLE](https://googleonlinesecurity.blogspot.ca/2014/10/this-poodle-bites-exploiting-ssl-30.html) attack. And in OkHttp 2.3 we dropped support for [RC4](https://en.wikipedia.org/wiki/RC4#Security). As with your desktop web browser, staying up-to-date with OkHttp is the best way to stay secure.

/// tip

The *path operation* for `swagger_ui_redirect` is a helper for when you use OAuth2.

If you integrate your API with an OAuth2 provider, you will be able to authenticate and come back to the API docs with the acquired credentials. And interact with it using the real OAuth2 authentication.

Swagger UI will handle it behind the scenes for you, but it needs this "redirect" helper.

///

            // BUILTIN with unknown type -> falls back to numeric toString
            SID unknownBuiltin = new SID(buildSidT((byte) 1, ident, 544), jcifs.SID.SID_TYPE_UNKNOWN, "BUILTIN", "ignored", false);
            assertEquals(unknownBuiltin.toString(), unknownBuiltin.toDisplayString());

            // BUILTIN with other type also returns acctName

If you are curious about how the raw OpenAPI schema looks like, FastAPI automatically generates a JSON (schema) with the descriptions of all your API.

You can see it directly at: <a href="http://127.0.0.1:8000/openapi.json" class="external-link" target="_blank">http://127.0.0.1:8000/openapi.json</a>.

It will show a JSON starting with something like:

```JSON
{
    "openapi": "3.1.0",
    "info": {
        "title": "FastAPI",

# Run tests for specific module
mvn test -pl fess-crawler
```

## Examples

### Web Crawling with Custom Rules

```java
// Create crawler with custom configuration
StandardCrawlerContainer container = new StandardCrawlerContainer();

// Configure HTTP client with custom settings
container.singleton("httpClient", HcHttpClient.class, client -> {
    client.setUserAgent("MyBot/1.0");

Any metadata changes on the source object version, such as metadata updates via PutObjectTagging, PutObjectRetention, PutObjectLegalHold and COPY api are replicated in a similar manner to target version, with the `X-Amz-Replication-Status` again cycling through the same states.

                FessWebResourceRoot.class.getName());

        // Verify constructor exists with Context parameter
        try {
            FessWebResourceRoot.class.getConstructor(Context.class);
            assertTrue("Constructor with Context parameter exists", true);
        } catch (final NoSuchMethodException e) {
            fail("Constructor with Context parameter should exist");
        }
    }

    public void test_methodsExist() {