4 Kicks

Prevent ASP.NET cookies from being sent on every css, js, img request(omaralzabir.com)

submitted by oazabiroazabir(1805) 7 months, 9 days ago

ASP.NET generates some large cookies if you are using ASP.NET membership provider. Especially if you are using the Anonymous provider, then a typical site will send 517 bytes of cookie on every css, js, image request. That's 60 GB worth useless upload for 1M page view. See how to prevent this.

2 comments |category: |Views: 30

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
bradygasterbradygaster(4897) - NoldorinNoldorin(829) - dpetersondpeterson(4397) - oazabiroazabir(1805)
Comments:

posted by dpetersondpeterson(4397) 7 months, 9 days ago 0

Yes. Cookie-less domains are a must-have, even if you aren't seeing 1M page-views a day. The reason being that it gives you the added benefit of loading static resources in parallel as most browsers will fetch simultaneously from separate sub-domains rather than in serial. So as your main content loads, images can load simultaneously without blocking.
Google pagespeed and YSlow both highly recommend cookie-less domains for static content.

Reply

posted by bradygasterbradygaster(4897) 7 months, 7 days ago 0

The numbers in this are scary, definitely motivational to at least look for a better method of getting it done.

Reply

information Login or create an account to comment on this story
Submit a Story
View upcoming stories
How else can I help?
Add our feeds to your site

Most Active Users

What's this?