Compression, https

Showing 1-12 of 12 messages
Compression, https daniel 5/20/11 8:21 AM
Does ServiceStack support compression, both in requests and responses? Does it suport https when self hosting? These are the only things that keep me from using it ;) 

Odp: Compression, https daniel 5/20/11 8:36 AM
I meant response compression and request decompression
Re: Compression, https mythz 5/20/11 8:42 AM
Hi Daniel,

If you use the RequestContext.ToOptimizedResultUsingCache it will return the most optimal result, i.e. Deflated/Gzipped output if the client (i.e. browser) supports it, example at:

Compression is not on by default but you can opt-in by returning your DTO in a CompressedResult to get this behaviour.
We don't do any special functionality to de-compress requests ourselves so it will only work if the web server/IIS is configured to uncompresses the request automatically for ASP.NET applications.

Self-hosting is available using the HttpListener, we've never hosted it using https ourselves but below are some tips on how to host a HttpListener with https:


On Fri, May 20, 2011 at 4:36 PM, daniel <> wrote:
I meant response compression and request decompression

- Demis

Odp: Re: Compression, https daniel 5/20/11 9:51 AM
Hi Demis, 

Thank You for response, I think RequestContext.ToOptimizedResultUsingCache will do just great for responses. Do You think it could be possible to decompress request using "Accessing the IHttpRequest and IHttpResponse using filters"?

Re: Re: Compression, https mythz 5/20/11 10:01 AM
Not with the Request and Response filters in ServiceStack since the DTO needs to be already materialized at that point.

You want to look for an IIS/ASP.NET configuration/filter that automatically decompresses deflated/gzipped requests that it receives for dynamic requests. 
It may even be on by default, you should just try it and see if it works.

Here's some info about configuring compression in IIS:

Odp: Re: Re: Compression, https daniel 5/20/11 12:05 PM
It looks like IIS only support reponses compression. Requests that I use are quite large (~40M) comparing to compressed (~4M).

Using WCF, I have written a custom message encoder ( I need solution that works both on .NET and Mono.

Re: Re: Re: Compression, https mythz 5/20/11 2:07 PM
Ok 40M web service requests sounds like a lot, too much.

Personally due to the resource constraints and fragility of handling of handling large messages I don't think processing 40M in realtime (i.e. as soon as you receive the request) is a winning strategy. 
Up to a certain size I would stop trying call web services with very large payloads and instead use the HTTP File Upload mechanism to transfer data instead which is much more resilient.

My preferred approach would be to package the payload on the client in an optimal format, HTTP upload it to the web service which would simply persist the message before an offline background thread or external service/process detects, unwraps and executes the request one at a time.

If you're considering doing something similar in the future then the RestFiles example shows how to process/save HTTP uploaded files:

Odp: Re: Re: Re: Compression, https daniel 5/20/11 11:54 PM
I transfer 40M (4M compressed) request only once a day to synchronize some data. All other transfers are quite small, I don't want to make additional file transfers when using WCF works just great already. 

What about: Global.asax and 

void Application_PreRequestHandlerExecute(object sender, EventArgs e)

Maybe I could do some decompression here? Do You think it's good place to start?

Odp: Re: Re: Re: Compression, https daniel 5/21/11 12:05 AM
   1: protected void Application_BeginRequest(object sender, EventArgs e)
   2: {
   3:     if (this.Request.Headers["Accept-Encoding"] != null
   4:         && this.Request.Headers["Accept-Encoding"].Contains("gzip")
   5:         && this.Request.Path.ToLower().EndsWith(".aspx"))
   6:     {
   7:         this.Response.Filter = new System.IO.Compression.GZipStream(this.Response.Filter, System.IO.Compression.CompressionMode.Compress, true);
   8:         this.Response.AddHeader("Content-encoding", "gzip");
   9:     }
  10: }

It's what I found for now.
Odp: Re: Re: Re: Compression, https daniel 5/21/11 12:08 AM
public void Application_BeginRequest() 
   Request.Filter = ...

Will it work with ServiceStack?

Re: Odp: Re: Re: Re: Compression, https mythz 5/21/11 3:13 AM
I don't see why not, ServiceStack is just a thin layer over ASP.NET's IHttpHandlers - if this works for normal ASP.NET web apps then it should work for ServiceStack.

Odp: Re: Odp: Re: Re: Re: Compression, https daniel 5/21/11 3:32 AM
Ok, that's great ;) I needed some confirmation if Application_BeginRequest will not colide with ServiceStack.