How to verify the identity of the client from the server?

I don't use Rails for my Server, I use PHP. But I think the approach is the same. Add a sort of a key to your Request.

I do it always as a POST value. Hardcode this key in your application. In PHP I do the following on my server in the first line of the scripts.

I don't use Rails for my Server, I use PHP. But I think the approach is the same. Add a sort of a key to your Request.

I do it always as a POST value. Hardcode this key in your application. In PHP I do the following on my server in the first line of the scripts: if ($_POST'secret'!

= "YOUR_KEY") { die('You are not allowed to use this Webservice. '); } Instead of YOUR_KEY I use strings as "UKZ6b79MKHK" and so on... So far it worked for my stuff. ;-) I hope my answer hepls you even if it's not Rails.

Sandro Meier.

– mr.pppoe May 22 at 6:09 There's no difference in. There's only a security reason to use POST. If you use a GET Request, your key is visible in the URL.

But normal user won't see your key. ;-) – Sandro Meier May 22 at 17:04.

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.