Reimplement buffer rewriting for headers about sozu HOT 2 CLOSED

In gitlab by @Geal on Apr 11, 2016, 19:26

This could be represented by a vector of this enum:

enum StuffToWrite {
  BufferSlice(start, end), // we can handle absolute positions, from the start of client data stream
  Data(Vec<u8>), // an owned vector containing things like additional headers
  Splice(usize), // indicates how much data should be copied through splicing
}

This way, we could encode useful scenarii like this one:

• buffer contains 1000 bytes of data
• don't pass the slice from 50 to 75 to the backend
• insert the string "Request-id: 1234"
• copy the rest of the buffer
• splice 30000 bytes of data afterwards

This would be encoded, with end of headers at 120, as [BufferSlice(0, 50), BufferSlice(75, 120), Data("Request-id: 1234"), BufferSlice(120, 1000), Splice(30000)]

The difficulty will probably lie in calculating positions and offsets, since because of deletions and inserts, there will be differences between input buffer position, and resulting stream position.

from sozu.

In gitlab by @Geal on Oct 3, 2016, 17:04

Done

from sozu.