Ajax over https you could if you wanted configure your server to require mutual authentication.
You could use Hash_chain to verify origin. On page load generate X times hash from random and send last hash with initial request (script tag) e.g. Hash100. Every next request send with HashLast-1.
On server B check whether hash(resieved_hash) is same as last one.
That would mean the client would be responsible for creating the hash values. Since I do not have control of the client side (only it's JS), wouldn't I have to store the cryptographic function in the client side, thus eliminating all security benefits. Also, how does it help me verify the authenticity of the web page of origin since the handshake occurs through AJAX?
– Nucleon Nov 16 '10 at 16:42 misunderstand problem in first place. Without control of site A there are no secure way. You can do it harder with minimized code and random names in request.. – Lauri Nov 22 '10 at 9:26.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.