12-11-2008 04:36 AM
Hi Folks,
We have a CSS 7.10.504 which seems to be splitting a request packet.
The packet is a standard POST request, however, at the end of the header 0d0a0d0a there is some additional data.
So we get header data ....0d0a0d0a then some more data.
CSS seems to be splitting this packet at the header boundary characters 0d0a0d0a.
Is this expected behaviour?
BR
Alan
12-11-2008 05:28 AM
I've checked a bit more and the client side packet shows a content length which implies that a body entity exists.
Would or could a CSS split the header and the entity body on packets on the server side?
12-15-2008 02:44 AM
I would not expect the CSS to do this.
But with 7.10 everything is possible.
Try 8.20 and if you have a sniffer trace that proves the CSS is splitting the packet, then open a service request.
BTW, it is normally acceptable to split TCP packets since TCP is a streaming protocol.
We could even send 1 byte per packet, this is still acceptable per RFC.
Gilles.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide