Chris_Phillips
Dec 06, 2006Nimbostratus
stream + content-length + chunking
Hi,
i have an xml application for which i'm using a stream profile to do hostname rewrites. as i've seen from deb's comments on a number of posts, the resulting variance in the payload size and the content-length can be overcome by using rechunking in the attached http profile. seemed great but...
1) there appears to be all sorts of crap added after each chunk according to wireshark (stuff like "10e", "d" and other tiny bits of raw hex)
2) the client app doesn't seem to like the chunking at all, possibly becasue of the above corrupting the xml, maybe just because it doesn't support it.
another option i saw was to change the content-length header manunally. this however causes the client software to hang until a timeout occurs, which is unacceptable.
essentially i really think i need the data to reach the client "correctly", without any hacks in the data (which i can't predict the contents of - so no idea how many replacements may occur). the only other option i can think of is to actually collect the full payload and do a regsub and ditch the stream profile, but this would presumably have a massive performance hit.
any takers?
Cheers
Chris