You can see the defined cookies in the docs UI at `/docs`:

<div class="screenshot">
<img src="/img/tutorial/cookie-param-models/image01.png">
</div>

/// info

Have in mind that, as **browsers handle cookies** in special ways and behind the scenes, they **don't** easily allow **JavaScript** to touch them.

If you go to the **API docs UI** at `/docs` you will be able to see the **documentation** for cookies for your *path operations*.

		switch {
		case isSysErrNotDir(err):
			// File path cannot be verified since one of
			// the parents is a file.
			return errFileAccessDenied
		case isSysErrPathNotFound(err):
			// This is a special case should be handled only for
			// windows, because windows API does not return "not a
			// directory" error message. Handle this specifically
			// here.
			return errFileAccessDenied
		}
	}
	return err
}

        assertEquals(rootCause, exception.getCause().getCause());
    }

    public void test_constructor_withSpecialCharactersInMessage() {
        // Test constructor with special characters in message
        String message = "Error with special chars: \n\t\r\"'<>&";
        SearchEngineClientException exception = new SearchEngineClientException(message);

        assertNotNull(exception);

eclipsebin

bin
gen
build
out
lib
generated

target
pom.xml.*
release.properties
local.properties

.idea
*.iml
*.ipr
*.iws
*.log
classes

obj

.DS_Store

# Special Mkdocs files
docs/4.x
docs/changelog.md
docs/contributing.md
docs/index.md

# jenv
/.java-version
/site/

   * available for all platforms and configurations. If that implementation is unavailable, this
   * method falls back to {@code getStackTrace}. Callers that require the special implementation can
   * check its availability with {@link #lazyStackTraceIsLazy()}.
   *
   * <p>The expected (but not guaranteed) performance of the special implementation differs from

            {
              "options": {
                "match": "null",
                "result": {
                  "text": "N/A"
                }
              },
              "type": "special"
            }
          ],
          "thresholds": {
            "mode": "percentage",
            "steps": [
              {
                "color": "green",
                "value": null
              }

        assertTrue(toStringResult.contains(message));
    }

    public void test_constructorWithScheduledJob_specialCharacters() {
        // Test with scheduled job that has special characters in toString
        ScheduledJob scheduledJob = new ScheduledJob() {
            @Override
            public String toString() {
                return "Job[name=\"Test & Job\", id='<123>']";
            }

# Request Parameters

Here's the reference information for the request parameters.

These are the special functions that you can put in *path operation function* parameters or dependency functions with `Annotated` to get data from the request.

It includes:

* `Query()`
* `Path()`
* `Body()`
* `Cookie()`
* `Header()`
* `Form()`
* `File()`

You can import them all directly from `fastapi`:

```python

        assertEquals(unicodeString, decoded);
    }

    public void test_special_characters_base64_encoding() {
        // Test that special characters are properly encoded/decoded
        String specialString = "******@****.***";
        String encoded = BaseEncoding.base64().encode(specialString.getBytes(StandardCharsets.UTF_8));

# Test generating the javadoc jars
./gradlew publishToMavenLocal -DRELEASE_SIGNING_ENABLED=false

# Generate the API docs
./gradlew dokkaHtmlMultiModule

mv ./build/dokka/htmlMultiModule docs/4.x

# Copy in special files that GitHub wants in the project root.
cat README.md | grep -v 'project website' > docs/index.md
cp CHANGELOG.md docs/changelogs/changelog.md
cp CONTRIBUTING.md docs/contribute/contributing.md

# Build the site locally