Problem when enabling Radcompression & SL 4

[Michele]

Hello,
I've tried to activate radcompression on my IIS7 server and SL application (4.0 SL), I got this exception

{System.Xml.XmlException: Unexpected end of file. Following elements are not closed: RelatesTo, Header, Envelope.
   at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, String res, String arg1, String arg2, String arg3)
   at System.Xml.XmlExceptionHelper.ThrowUnexpectedEndOfFile(XmlDictionaryReader reader)
   at System.Xml.XmlBufferReader.ReadUniqueId()
   at System.Xml.XmlBinaryReader.ReadElementContentAsUniqueId()
   at System.ServiceModel.Channels.RelatesToHeader.ReadHeader(XmlDictionaryReader reader, AddressingVersion version, String actor, Boolean mustUnderstand, Boolean relay)
   at System.ServiceModel.Channels.MessageHeaders.ReadBufferedHeader(XmlDictionaryReader reader)
   at System.ServiceModel.Channels.MessageHeaders.Init(MessageVersion version, XmlDictionaryReader reader, IBufferedMessageData bufferedMessageData)
   at System.ServiceModel.Channels.BufferedMessage..ctor(IBufferedMessageData messageData)
   at System.ServiceModel.Channels.BinaryMessageEncoderFactory.BinaryMessageEncoder.ReadMessage(ArraySegment`1 buffer, BufferManager bufferManager, String contentType)
   at System.ServiceModel.Channels.HttpInput.DecodeBufferedMessage(ArraySegment`1 buffer, Stream inputStream)}

from the AuthenticationService.svc as far as it calls the IsLoggedIn method... if I disable the compression everithing works fine...any suggestion?

I'm using 2012.1.215.40 version of dll...any suggestion?

[Martin]

Hello Paolo,

I would suggest that you review this forum thread. As stated in the last post, the issue is already reported to Microsoft.

I hope this helps

Kind regards,
Martin
the Telerik team

[Michele]

it's a 15month old post... so no way of using compression between SL4 and WCF?

[Martin]

Hello,

I am afraid that since the issue is accepted and confirmed by Microsoft, we can not help much in resolving the problem. What you can try as a temporary resolution (lets hope MS will get it fixed in the future release) is to try some of the workarounds provided in the MS connect issue tracker.

Greetings,
Martin
the Telerik team