LocalStorage Exploit on Chrome, Safari (iOS and desktop), and IE
1–10 of 10 posts
Re: LocalStorage Exploit on Chrome, Safari (iOS and desktop), and IE
#2Re: LocalStorage Exploit on Chrome, Safari (iOS and desktop), and IE
#3I don’t see a good way around this. If website enforce a domain limit within which all subdomains have to fit, then applications hosted on shared domains such as Heroku or AppSpot.com will squeeze each other out.
Re: LocalStorage Exploit on Chrome, Safari (iOS and desktop), and IE
#4I don’t see a good way around this. If website enforce a domain limit within which all subdomains have to fit, then applications hosted on shared domains such as Heroku or AppSpot.com will squeeze each other out.
Well, supposedly Firefox is immune to it. So why not just take from that?
Re: LocalStorage Exploit on Chrome, Safari (iOS and desktop), and IE
#5Re: LocalStorage Exploit on Chrome, Safari (iOS and desktop), and IE
#6I don’t see a good way around this. If website enforce a domain limit within which all subdomains have to fit, then applications hosted on shared domains such as Heroku or AppSpot.com will squeeze each other out.
Re: LocalStorage Exploit on Chrome, Safari (iOS and desktop), and IE
#7This is a repost.
Re: LocalStorage Exploit on Chrome, Safari (iOS and desktop), and IE
#8I don’t see a good way around this. If website enforce a domain limit within which all subdomains have to fit, then applications hosted on shared domains such as Heroku or AppSpot.com will squeeze each other out.
Re: LocalStorage Exploit on Chrome, Safari (iOS and desktop), and IE
#9I don’t see a good way around this. If website enforce a domain limit within which all subdomains have to fit, then applications hosted on shared domains such as Heroku or AppSpot.com will squeeze each other out.
Re: LocalStorage Exploit on Chrome, Safari (iOS and desktop), and IE
#10This is a repost.