Last post Dec 30, 2014 11:47 PM by gtscdsi
Dec 29, 2014 12:57 PM|AdamWalsh|LINK
I've been struggling with this one for a while and i'd like an official answer. I configured IIS to compress all dynamic/static content (as a test) and everything seems to be working fine besides the SignalR responses. The SignalR responses come back with
the Content-Encoding:gzip header missing which tells me compression is not happening. Is SignalR doing something special so that compression doesn't happen? Someone posted on stackoverflow about implementing compression for longpolling for the .NET client
a way to have equivalent functionality? Maybe there's a way to generically implement compression in the SignalR server infrastructure?
I'm exclusively using LongPolling and don't care about streaming. I just want gzip compression for our larger (5-50mb) requests. I could manually compress and decompress in the hub and clientside code but i'm concerned that i'll be reinventing the wheel
and there might be a better way to do it. Thoughts?
Dec 30, 2014 09:51 PM|gtscdsi|LINK
I am looking for someone can answer this question. Thank you.
Dec 30, 2014 11:47 PM|gtscdsi|LINK
According to the feedback from signalR team,
SignalR manually disables compression because it messes with our streaming responses for the Server Sent Events and Forever Frame transports. Send requests and long polling requests should still
be compressed but might be wrong.