assertNull(exception.getCause());
    }

    @Test
    public void test_constructor_withSpecialCharacters() {
        // Test constructor with special characters
        String type = "Token-Type_123!@#";
        String message = "Error: Token contains special characters <>&\"'";
        InvalidAccessTokenException exception = new InvalidAccessTokenException(type, message);

        assertEquals(type, exception.getType());

        // Setup
        final String message = "Error: Failed to authenticate user <******@****.***> with special chars: #$%&*()!@";
        final VaMessenger<FessMessages> messageCode = messages -> messages.addErrorsSsoLoginError(UserMessages.GLOBAL_PROPERTY_KEY);
        final Exception cause = new RuntimeException("Special cause: \n\t\r");

        // Execute

            assertTrue(exception.toString().contains("TransportException"));
        }

        @Test
        @DisplayName("Should handle special characters in message")
        void testSpecialCharactersInMessage() {
            String message = "Error: \n\t\r\\ \"special\" 'chars' @#$%^&*()";
            TransportException exception = new TransportException(message);

            assertEquals(message, exception.getMessage());

        bufferIndex += 12; // 10 reserved

        return bufferIndex - start;
    }

    @Override
    int readBytesWireFormat(final byte[] buffer, final int bufferIndex) {
        // handled special in SmbTransport.doRecv()
        return 0;
    }

    @Override
    public String toString() {

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

/// info | Información

Ten en cuenta que, como los **navegadores manejan las cookies** de maneras especiales y detrás de escenas, **no** permiten fácilmente que **JavaScript** las toque.

Si vas a la **UI de la documentación de la API** en `/docs` podrás ver la **documentación** de las cookies para tus *path operations*.

        assertEquals("Large list size should match", original.size(), deserializedList.size());
    }

    /**
     * Test that serializer handles special characters correctly
     */
    @Test
    public void test_serializeDeserialize_specialCharacters() {
        String original = "Special: !@#$%^&*(){}[]<>?/\\|~`±§";

        byte[] serialized = serializer.fromObjectToBinary(original);

        } catch (ConfigPropertyNotFoundException e) {
            // Expected exception
            assertNotNull(e);
        }
    }

    // Test special characters in property values
    @Test
    public void test_get_specialCharacters() {
        String testKey = "special.chars";
        String specialValue = "!@#$%^&*()_+-=[]{}|;':\",./<>?";
        System.setProperty(Constants.FESS_CONFIG_PREFIX + testKey, specialValue);

        // HashCode for empty string
        assertEquals(0, info.hashCode()); // Empty string has hashCode of 0
    }

    @Test
    @DisplayName("Test with special characters in names")
    void testWithSpecialCharacters() {
        String specialName = "Share$\\Special/Name:*?";
        String specialRemark = "Remark with\nnewline\tand\rtabs";

        SmbShareInfo info = new SmbShareInfo(specialName, 0, specialRemark);

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

## Forbid Extra Query Parameters { #forbid-extra-query-parameters }

In some special use cases (probably not very common), you might want to **restrict** the query parameters that you want to receive.

You can use Pydantic's model configuration to `forbid` any `extra` fields:

             * Eclipse. This is because Eclipse flattens main and test
             * dependencies into a single dependency. Because Eclipse is
             * "special".... */
            return;
        }

        Configuration testImplementationConfig = project.getConfigurations().getByName("testImplementation");
        testImplementationConfig.getDependencies().all(dep -> {