Well... the authorization header was a good idea, but src attributes can't pass in headers. So, if we store it in a cookie, it'll go along with all the future requests, including src requests.
This will also allow the multiple login issue to be more easily solved
Also data: src addresses are out since they're not supported in IE<10
Well... the authorization header was a good idea, but src attributes can't pass in headers. So, if we store it in a cookie, it'll go along with all the future requests, including src requests.
This will also allow the multiple login issue to be more easily solved
Also data: src addresses are out since they're not supported in IE<10