O
Ostap Radkovskiy
The problem:
There is web service and its client (.NET 1.1).
The session support on web service is turned on.
After the number of successful roundtrips between client and server, web
service sends to client corrupted packet like this (the number of comments
on top could vary):
<!-- Here is a dummy timestamp from the server: 14:45:05 -->
<!-- Here is a dummy timestamp from the server: 14:45:10 -->
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd=http://www.w3.org/2001/XMLSchema<soap:Body>correct packet body inside - removed just for
sample</soap:Body>
</soap:Envelope>
Comments on top you see - the reason of Xml readers crash on client.
I've implemented a proxy to remove the comments <!-- ... --> (the cause of
crash) - however this only solved part of the problem - the other part is
that server after the mentioned packet should send HTTP/1.1 100 Continue -
and it does not!
How to fix? It appears to be .NET bug or something. Is there some solution,
workaround or patch?
There is web service and its client (.NET 1.1).
The session support on web service is turned on.
After the number of successful roundtrips between client and server, web
service sends to client corrupted packet like this (the number of comments
on top could vary):
<!-- Here is a dummy timestamp from the server: 14:45:05 -->
<!-- Here is a dummy timestamp from the server: 14:45:10 -->
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd=http://www.w3.org/2001/XMLSchema<soap:Body>correct packet body inside - removed just for
sample</soap:Body>
</soap:Envelope>
Comments on top you see - the reason of Xml readers crash on client.
I've implemented a proxy to remove the comments <!-- ... --> (the cause of
crash) - however this only solved part of the problem - the other part is
that server after the mentioned packet should send HTTP/1.1 100 Continue -
and it does not!
How to fix? It appears to be .NET bug or something. Is there some solution,
workaround or patch?