security - Send Cookie on every request to identify user? -
i'm not getting head around whole session-management thing.
i've implemented this take care login process , this example protect services xsrf attacks.
but i'm having wonder:
- if turn on ssl, cookie sent before secure connection built up? session id (the cookie) ever secure?
- is save send cookie on each request identify user? e.g. if user wants view his/her settings, make sure it's not fake request tries retrieve settings user. clear mean that?
i send session id on each request, compare session id in database , if request-token (xsrf securiy) fine execute request - or overhead?
i'm still not quite confident if i'm doing here 100% correct , want make sure don't unnecessarily break security measures i've spent time implementing.
ssl or tls connections established before http request sent on wire, data in request encrypted.
i'm not sure understand second question, lot of web applications use cookie based authentication identify user. cookies automatically sent website, have protect against csrf attacks.
Comments
Post a Comment