Class ClientChatter

The ClientChatter object, exposed as the oRequest object on the Session object, represents a single web request.

Inheritance

System.Object

ClientChatter

Namespace: Fiddler

Assembly: FiddlerCore.dll

Syntax

public class ClientChatter : Object

Fields

pipeClient

The ClientPipe object which is connected to the client, or null.

Declaration

public ClientPipe pipeClient

Field Value

ClientPipe

Properties

bClientSocketReused

Was this request received from a reused client connection? Looks at SessionFlags.ClientPipeReused flag on owning Session.

Declaration

public bool bClientSocketReused { get; }

Property Value

System.Boolean

BufferRequest

Controls whether the request body is streamed to the server as it is read from the client.

Declaration

[CodeDescription("Controls whether the request body is streamed to the server as it is read from the client.")]
public bool BufferRequest { get; set; }

Property Value

System.Boolean

headers

HTTP Headers sent in the client request, or null.

Declaration

public HTTPRequestHeaders headers { get; set; }

Property Value

HTTPRequestHeaders

host

Note: This returns the request's HOST header, which may include a trailing port #. If the Host is an IPv6 literal, it will be enclosed in brackets '[' and ']'

Declaration

public string host { get; }

Property Value

System.String

InboundPort

Returns the port on which Fiddler read the request (typically 8888)

Declaration

[CodeDescription("Returns the port on which Fiddler read the request (typically 8888). Only available while the request is alive.")]
public int InboundPort { get; }

Property Value

System.Int32

Item[String]

Simple indexer into the Request Headers object

Declaration

public string this[string sHeader] { get; set; }

Parameters

System.String sHeader

Property Value

System.String

Methods

FailSessionAsync(Int32, String, String)

Send a HTTP/XXX Error Message to the Client, calling FiddlerApplication.BeforeReturningError and DoReturningError in FiddlerScript. Note: This method does not poison the Server pipe, so if poisoning is desired, it's the caller's responsibility to do that. Note: Because this method uses Connection: close on the returned response, it has the effect of poisoning the client pipe

Declaration

public Task FailSessionAsync(int iError, string sErrorStatusText, string sErrorBody)

Parameters

System.Int32 iError Response code

System.String sErrorStatusText Response status text

System.String sErrorBody Body of the HTTP Response

Returns

System.Threading.Tasks.Task

SendBodyAsync(Byte[], Int32, Boolean)

Send the response body back to the client

Declaration

public Task<int> SendBodyAsync(byte[] arrBodyBytes, int length, bool final = true)

Parameters

System.Byte[] arrBodyBytes Array containing a part or the whole body

System.Int32 length How many bytes to send

System.Boolean final True if this is the final part of the body to send

Returns

System.Threading.Tasks.Task<System.Int32> The size of the bytes being transferred

StreamHTTP2BodyPart(Session, Int64, out Byte[], out Boolean)

Stream whatever data frames are present in the buffer at the specified offset

Declaration

public long StreamHTTP2BodyPart(Session oS, long offset, out byte[] arrResult, out bool isFinal)

Parameters

Session oS The parent session of this connection

System.Int64 offset Offset in the received data to start leaking the body from

System.Byte[] arrResult Output array buffer that will hold the parsed data

System.Boolean isFinal True if the last parsed frame has an 'EndOfStream' flag set

Returns

System.Int64 The parser's final position (offset) in the data stream. This can be less than the data strem length if extra frames or incomplete frames are present.