_2021-11-21_

 *  Fix: Don't fail HTTP/2 responses if they complete before a `RST_STREAM` is sent.


## Version 4.9.2

_2021-09-30_

 *  Fix: Don't include potentially-sensitive header values in `Headers.toString()` or exceptions.
    This applies to `Authorization`, `Cookie`, `Proxy-Authorization`, and `Set-Cookie` headers.
 *  Fix: Don't crash with an `InaccessibleObjectException` when running on JDK17+ with strong
    encapsulation enabled.

    @DisplayName("Methods should handle empty buffer")
    void testMethodsWithEmptyBuffer() {
        // Arrange
        byte[] emptyBuffer = new byte[0];

        // Act & Assert - These should not throw exceptions
        assertEquals(0, response.writeSetupWireFormat(emptyBuffer, 0));
        assertEquals(0, response.writeParametersWireFormat(emptyBuffer, 0));
        assertEquals(0, response.writeDataWireFormat(emptyBuffer, 0));

    private final RuntimeException ex;

    private ThrowingIterator(RuntimeException ex) {
      this.ex = ex;
    }

    @Override
    public boolean hasNext() {
      // IteratorTester doesn't expect exceptions for hasNext().
      return true;
    }

    @Override
    public E next() {
      ex.fillInStackTrace();
      throw ex;
    }

    @Override
    public void remove() {

            });

            thread1.start();
            thread2.start();
            thread1.join();
            thread2.join();

            // Then - no exceptions should occur
            assertTrue(true);
        }
    }

import org.apache.maven.artifact.Artifact;
import org.apache.maven.artifact.repository.ArtifactRepository;
import org.apache.maven.artifact.repository.ArtifactRepositoryPolicy;

/**
 * Base class for artifact resolution exceptions.
 *
 */
public class AbstractArtifactResolutionException extends Exception {
    private String groupId;

    private String artifactId;

    private String version;

    private String type;

        }
        checkExceptionClassValidity(exceptionClass);

        /*
         * It's very unlikely that any loaded Futures class will see getChecked called with more
         * than a handful of exceptions. But it seems prudent to set a cap on how many we'll cache.
         * This avoids out-of-control memory consumption, and it keeps the cache from growing so

 * credentials are retrieved from the {@code jcifs.smb.client.domain},
 * {@code jcifs.smb.client.username}, and {@code jcifs.smb.client.password}
 * properties.
 * <p>
 * Read <a href="../../../authhandler.html">jCIFS Exceptions and
 * NtlmAuthenticator</a> for related information.
 *
 * @deprecated use {@link NtlmPasswordAuthenticator} instead
 */
@Deprecated
public class NtlmPasswordAuthentication extends NtlmPasswordAuthenticator {

        verify(fd, never()).markClosed();
    }

    @Test
    @DisplayName("available() wraps SmbException to IOException")
    void available_wrapsException() throws Exception {
        // Verify exceptions from th.send are converted to IOException via seToIoe
        SmbPipeInputStream stream = newStreamWithMinimalStubs(true);

        when(handle.ensureOpen()).thenReturn(fd);
        when(fd.getTree()).thenReturn(tree);

Ahora, obtén los datos del usuario desde la base de datos (falsa), usando el `username` del campo del form.

Si no existe tal usuario, devolvemos un error diciendo "Incorrect username or password".

Para el error, usamos la excepción `HTTPException`:

{* ../../docs_src/security/tutorial003_an_py310.py hl[3,79:81] *}

### Revisa el password

En este punto tenemos los datos del usuario de nuestra base de datos, pero no hemos revisado el password.

   * to perform more efficiently.
   *
   * <p>An escaper is expected to be able to deal with any {@code char} value, so this method should
   * not throw any exceptions.
   *
   * @param c the character to escape if necessary
   * @return the replacement characters, or {@code null} if no escaping was needed
   */
  protected abstract char @Nullable [] escape(char c);

  /**