using soap with a .net client, a soap server sends a document with a
string structure. In the string structure is a vertical tab (0x0b).
The soap server converts the tab to  before transmitting. This
seems to be a valid xml document upon transmitting.
however, the client receives this document and throws the exception
({"'\v', hexadecimal value 0x0B, is an invalid character. Line 1,
position 468." })
Why is it that the validation is being done on a document with 0x0B and
not , shouldn't the conversion of the data occur after the
validation?
How do I get around this and send this data without base64 encoding it.
I don't have control over client applications that also use this soap
interface, so I'm reluctant to make a change like that.
what the string looks like over the wire is below
tag data begins at 3A6
0000039F 6f 6d 6d 65 6e 74 3e 26 23 31 32 35 31 33 3b 26 omment>&
#12513;&
000003AF 23 31 32 35 33 31 3b 26 23 31 32 34 39 36 3b 2d #12531;&
#12496;-
000003BF 26 23 36 35 34 33 36 3b 26 23 36 35 33 39 31 3b ワ
ッ
000003CF 26 23 36 35 34 30 34 3b 26 23 36 35 33 38 38 3b シ
ャ
000003DF 2d 28 26 23 39 33 34 3b 33 30 29 26 23 78 42 3b -(Φ
30)
thanks,
dan