Today I was asked why json responses from WebApi was not being gzipped since it brought down our score on Google Page Speed.
So yet again I started my ongoing fight with Google Page Speed. It turns out that we had issues making IIS gzip application/json data. Since we do not have direct access to the production environment I decided that we would be better off simply gzipping the response content in code where and when we wanted to.
So I thought there must be an ActionFilterAttribute for this already but it turns out there is not.
I searched and searched and came by this fine solution which adds a MessageHandler that gzips responses.
But I would so much prefer just to be able to mark a method or a controller class with an attribute, that just seems cleaner.
So I decided to write the following ActionFilterAttribute :
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 |
using System; using System.Linq; using System.Web.Http.Filters; namespace LaubPlusCo.WebApi.Compression { [AttributeUsage(AttributeTargets.Class | AttributeTargets.Method)] public class CompressFilter : ActionFilterAttribute { public override void OnActionExecuted(HttpActionExecutedContext context) { var acceptedEncoding = context.Response.RequestMessage.Headers.AcceptEncoding.First().Value; if (!acceptedEncoding.Equals("gzip", StringComparison.InvariantCultureIgnoreCase) && !acceptedEncoding.Equals("deflate", StringComparison.InvariantCultureIgnoreCase)) { return; } context.Response.Content = new CompressedContent(context.Response.Content, acceptedEncoding); } } } |
Where CompressedContent is a class that derives from HttpContent highly inspired by the post I referenced above.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 |
using System; using System.IO; using System.IO.Compression; using System.Net; using System.Net.Http; using System.Threading.Tasks; namespace LaubPlusCo.WebApi.Compression { public class CompressedContent : HttpContent { private readonly string _encodingType; private readonly HttpContent _originalContent; public CompressedContent(HttpContent content, string encodingType = "gzip") { if (content == null) { throw new ArgumentNullException("content"); } _originalContent = content; _encodingType = encodingType.ToLowerInvariant(); foreach (var header in _originalContent.Headers) { Headers.TryAddWithoutValidation(header.Key, header.Value); } Headers.ContentEncoding.Add(encodingType); } protected override bool TryComputeLength(out long length) { length = -1; return false; } protected override Task SerializeToStreamAsync(Stream stream, TransportContext context) { Stream compressedStream = null; switch (_encodingType) { case "gzip": compressedStream = new GZipStream(stream, CompressionMode.Compress, true); break; case "deflate": compressedStream = new DeflateStream(stream, CompressionMode.Compress, true); break; default: compressedStream = stream; break; } return _originalContent.CopyToAsync(compressedStream).ContinueWith(tsk => { if (compressedStream != null) { compressedStream.Dispose(); } }); } } } |
And now we can use the CompressFilter attribute on classes like this:
|
1 2 3 4 5 |
[CompressFilter] public class MyController : ApiController { // ... } |
Or on methods like this:
|
1 2 3 4 5 6 7 8 9 |
public class MyController : ApiController { [HttpGet] [CompressFilter] public IHttpActionResult Get() { // } } |
When to use it?
It is best to let IIS perform the compression instead of doing it in code.
But if this for some reason is not possible to configure or if you for some reason only want selected responses to be gzipped then this attribute will do the job just perfect.
There is also a fine line for when it makes sense to let the server use time on gzipping the response. This is why IIS has an optional config attribute on the httpCompression element for setting a minimum file size before compression (minFileSizeForComp).
Hope this helps someone out there.
Anders Laub Christoffersen
Anders has been working with Sitecore for over a decade and has in this time been the lead developer and architect on several large scale enterprise solutions all around the world. Anders was appointed the title of Sitecore Technical MVP in 2014 and has been re-appointed the title every year since then.
- Web |
- More Posts