views:

54

answers:

1

It's pretty well known that Google Ads doesn't support HTTPS, but since I store my user's session in a bearer token/cookie I feel the need to encrypt this information... at a minimum so I can protect my end users from being hacked.

What are my choices? I'm sure someone has come across this before. Ideas that may work include

  • Changing how I do website membership
  • Using something else other than AdSense (MSN?, anyone else)
  • Complaining to Google that I can't track my users if AdSense is on
  • Finding a different way to monetize my site (aka changing my business model)
+1  A: 

Option 3 won't do anything, #4 could be a lot of work, #2.. AdSense is still king.

That leaves option 1 - simplest option in my opinion. Are you using any frameworks?

Radu
@Radu I'm using ASP.NET Membership API. This is currently interfacing with WIF where I use ADFS and my own STS provider.
MakerOfThings7