Payload before encryption :
HTTP/1.1 200 OK
Authorization: password
Content-Encoding: UTF-8
Content-Length: 138
{ "command" : "delete all records" }
Payload after encrypting Authorization header :
HTTP/1.1 200 OK
Authorization: spxnxkoJX+O1iatF6gco9Q==
Content-Encoding: UTF-8
Content-Length: 138
{ "command" : "delete all records" }
Protocol is NOT over SSL.
EDIT
In our project, my senior added this extra layer of security(as per his opinion), with which I am not agree. As per my opinion, this will add an extra cost of encryption and decryption of header value and without any security benefit.
I want to ensure, if he is really right?
I'm struggling to imagine why the HTTP response should require authorization. I've only ever seen it in HTTP requests. Further, where the server did need to prove itself to the client (in a world without SSL) why is the being sent as a header and not in the body of the response.
– symcbean Jul 13 '16 at 10:14