Skip to main content

Serve static content from a cookieless domain

While performance testing an Angular.js website, I ran the site through a few benchmarking tools like Google PageSpeed Insights, Yahoo’s YSlow, and so on…

One of the recommendations that these tools returned is ‘Serve static content from a cookieless domain’. Although there is some discussion going on if this recommendation actually makes sense, I spend some time reconfiguring IIS to get this working so I can measure the impact myself.

Here are the steps I took to get it working:

  • Inside IIS I configured 2 websites:

image

    • A Default Web Site that listens on port 80 and has a custom host header configured(I used www.test.com as an example)

image

    • A second website CDN that also listens on port 80 and has a different custom header configured(I used cdn.test.com for this one)

image

  • For the CDN site, disable ASP.NET session state, this prevents cookies from being returned by ASP.NET.
    • Click on Session State.
    • Set the Session State Mode on Not enabled and click on Apply.

image

image

  • Copy your static content(images, css, javascript) over to the CDN site
  • Inside your website, change the urls for the static content to point to the CDN site.
  • Run your application
    • If you look at the requests to the default website, you see that cookies are sent with the request:

image

    • But if we look at a request to the CDN, no cookies are included:

image

Labels

Labels:

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...
Read more