internal void OnOnReadResponseBuffer(object sender, RawReadEventArgs e) { EventHandler <RawReadEventArgs> handler = OnReadResponseBuffer; if (handler != null) { handler(this, e); } }
static void FiddlerApplication_OnReadResponseBuffer(object sender, RawReadEventArgs e) { var rSession = e.sessionOwner.Tag as NetworkSession; if (rSession != null) { rSession.LoadedBytes += e.iCountOfBytes; } }
private void OnBufferWrite(object sender, RawReadEventArgs e) { if (e.sessionOwner.TryGetProcessName(out string processName)) { if (ProcessHandler.TryMatchProcess(processName, out PProcess pp)) { pp.Inbound += e.iCountOfBytes; } } InboundTotal += e.iCountOfBytes; }
// This event handler is called on every socket read for the HTTP Response. You almost certainly don't want // to add a handler for this event, but the code below shows how you can use it to mess up your HTTP traffic. static void FiddlerApplication_OnReadResponseBuffer(object sender, RawReadEventArgs e) { // NOTE: arrDataBuffer is a fixed-size array. Only bytes 0 to iCountOfBytes should be read/manipulated. // // Just for kicks, lowercase every byte. Note that this will obviously break any binary content. for (int i = 0; i < e.iCountOfBytes; i++) { if ((e.arrDataBuffer[i] > 0x40) && (e.arrDataBuffer[i] < 0x5b)) { e.arrDataBuffer[i] = (byte)(e.arrDataBuffer[i] + (byte)0x20); } } Console.WriteLine(String.Format("Read {0} response bytes for session {1}", e.iCountOfBytes, e.sessionOwner.id)); }
private void FiddlerApplication_OnReadResponseBuffer(object sender, RawReadEventArgs e) { }
static void rconClient_RawRead(object sender, RawReadEventArgs e) { //Log.Info("RawRead - IsFromServer: " + e.Packet.IsFromServer + " - IsResponse: " + e.Packet.IsResponse + " - Sequence: " + e.Packet.Sequence + " - Words: " + string.Join(" :: ", e.Packet.Words.ToArray())); }