How would a user stay logged in to a REST-based website?

Posted by unforgiven3 on Stack Overflow See other posts from Stack Overflow or by unforgiven3
Published on 2010-12-23T19:48:50Z Indexed on 2010/12/23 19:54 UTC
Read the original article Hit count: 230

A year or so ago I asked this question: Can you help me understand this? “Common REST Mistakes: Sessions are irrelevant”. My question was essentially this:

Okay, I get that HTTP authentication is done automatically on every message - but how? Is the username/password sent with every request? Doesn't that just increase attack surface area? I feel like I'm missing part of the puzzle.

The answers I received made perfect sense in the context of a mobile (iPhone, Android, WP7) app - when talking to a REST service, the app would just send user credentials along with each request. That worked great for me.

But now, I would like to better understand how one would secure a REST-like website, like StackOverflow itself or something like Reddit. How would things work if it was a user logged in via a web browser instead of logged in via an iPhone app?

  • What happens when a user logs in? Are the credentials saved in the browser somehow?
  • How would the browser know what credentials to send with subsequent REST requests?
  • What if it's a JavaScript call to a webservice? How would the JavaScript call include user credentials?

I'll be quite frank: my understanding of security when it comes to websites is pretty limited. I enjoyed working with REST services from an app perspective, but now I want to try and build a website that is based on REST principles, and I'm finding myself to be pretty lost.

If there is anything in the above question that is unclear that you'd like me to clarify, please leave a comment and I'll address it.

© Stack Overflow or respective owner

Related posts about web-applications

Related posts about session