Package org.mockserver.netty.proxy.relay

package org.mockserver.netty.proxy.relay
  • Classes
    Class
    Description
    BinaryRelay
    One binary client connection's single upstream connection, and the bytes relayed between the two as they arrive.
    DownstreamProxyRelayHandler
     
    ExpectContinueInboundHttp2ToHttpAdapter
    The proxy client's side of the CONNECT/SOCKS relay's HTTP/2 tunnel, handing each request on once, with its whole body.
    LoopbackHttp1ResponseErrorHandler
    Answers the proxy client with a 502 when the CONNECT/SOCKS relay's HTTP/1.1 loopback fails to decode a response (a corrupt compressed body, one larger than maxRequestBodySize, or one the codec marks as failed) before its head has been relayed.
    LoopbackHttp2ConnectionCloseHandler
    Ends the proxy client's HTTP/2 streams at once when the CONNECT/SOCKS relay's HTTP/2 loopback connection closes, for any reason, instead of leaving them to Netty's 30 s graceful-shutdown timeout.
    LoopbackHttp2StreamErrorHandler
    Answers the proxy client's HTTP/2 stream when the CONNECT/SOCKS relay's HTTP/2 loopback stream for it ends without a response: the response failed to decode, passed maxRequestBodySize, or MockServer reset the stream.
    LoopbackHttp2StreamIdRemapper
    Gives each request the CONNECT/SOCKS relay writes to its HTTP/2 loopback a loopback stream id of its own, and puts the proxy client's stream id back on the response.
    LoopbackRelaySignalHandler
    On MockServer's side of an HTTP/1.1 relay loopback, after its codec: tells the tunnel's relay what the bytes on the loopback cannot.
    RelayConnectHandler<T>
     
    RelayLoopbackAddresses
    The local addresses of the loopback connections RelayConnectHandler opens to MockServer, each with the proxy client's channel of its tunnel, so the accepting side can tell its own relay's loopback leg from a client that merely sends the same PROXIED_ preamble, and can reach the tunnel's other leg.
    UpstreamProxyRelayHandler
     
    UpstreamReply
    What a relay does with the upstream's reply to one message it forwards: relays it to the client (the default), drops it, or drops it and writes other bytes to the client in its place once it has ended.