I'm specifically interested in how users perform authorized / authenticated operations on a web API.

Are authentication cookies compatible with the REST philosophy, and why?

  • exact duplicate of restful-authentication
    – user7519
    Commented Mar 22, 2012 at 18:21
  • 1
    @JarrodRoberson My understanding was that answers on another site wouldn't qualify the question as duplicate on here Commented Mar 25, 2012 at 16:42
  • 7
    @JarrodRoberson based on each site's FAQs, I would argue the question belongs on this site and not Stack Overflow. I'm interested in design methodology / philosophy and tradeoffs regarding this aspect of RESTful architecture. Stack Overflow is meant for implementation questions, where this site is more about design methodologies and tradeoffs. Commented Mar 26, 2012 at 14:03
  • 1
    I agree with @BrandonLinton here, the question is too broad for Stackoverflow, it is one regarding architecture and design methodology. The OP wants best practice and patterns, suggestions and gotchas - not a specific answer - hence no language has been specified. Hence, it belongs here.
    – dooburt
    Commented Dec 24, 2012 at 15:33

3 Answers 3


An ideal ReSTful service allows clients (which may not be in-browser) to perform any needed task in one request; because the full state needed to do that is held by the client, not the server. Since the client has full control of the state, it can create the state on its own (if that is legitimate), and only talk to the API to "get 'er done".

Requiring cookies can make that difficult. For clients besides browsers, managing cookies is a pretty big inconvenience compared to query params, plain request headers or the request body. On the other hand, In browser, using cookies can make lots of things much simpler.

So an API might first look in the Authorization header for the authentication data it needs, since that's probably the place where non-browser clients will prefer to put it, but to simplify and streamline browser-based clients, it might also check for a session cookie for server side log in, but only if the regular Authorization header was missing.

Another example might be a complex request that normally requires lots of parameters set. A non interactive client would have no trouble jamming all of that data into one request, but a HTML form based interface might prefer to break the request into several pages (something like a set of 'wizard' pages) so that users aren't presented with options that are not applicable based on previous selections. All of the intermediate pages could store the values in client side cookies, so that only the very last page, where the user actually submits the request, has any server side effect at all. The API could look for the needed attributes in the request body, and fall back to looking at cookies if the needed parameters weren't there.

Edit: in RE to @Konrad's comment below:

Tokens in comparison are harder to implement especially because you can't easily invalidate the token without storing them somewhere.

er... you are validating the cookies on the server side, right? Just because you told the browser to discard a cookie after 24 hours doesn't mean it will. That cookie could be saved by a highly technical user and reused long after it has "expired".

If you don't want to store session data on the server side, you should store it in the token (cookie or otherwise). A self contained auth token is sometimes called a Macaroon. How this is passed between client and server (whether by cookie, as extra headers, or in the request entity itself) is totally independent of the authentication mechanism itself.

  • 7
    +1, I definitely like the practicality of using the Authorization header but "falling back" to cookies depending on what works best for the client. Commented Mar 26, 2012 at 14:17
  • 1
    I disagree with "For clients besides browsers, managing cookies is a pretty big inconvenience...". Mostly HTTP client libraries support cookies, for example, with HttpClient in .NET you can use cookies without any problem and you don't really need to think about it. Tokens in comparison are harder to implement especially because you can't easily invalidate the token without storing them somewhere.
    – Konrad
    Commented Aug 31, 2018 at 12:26
  • 2
    @Konrad just because it is easy in some non-browser clients doesn't mean it's easy in all of them. It's fine if you only need to support the particular client you happen to use, but i interpreted the question to be about public facing API's. in curl or wget, managing cookies is pretty darn inconvenient and you really do have to think about them a bunch. I replied to your other point by editing my answer. Commented Sep 1, 2018 at 15:10
  • 1
    Beware that simply accepting cookies opens up CSRF vulnerabilities. See also security.stackexchange.com/a/166798 Commented Oct 18, 2018 at 12:37
  • For clients besides browsers, managing cookies is a pretty big inconvenience compared to query params, plain request headers or the request body. Do you have a good resource explaining that further? Taking Python's requests library as an example, passing cookies works pretty much the same as query parameters or headers, at least on a syntax level.
    – bluenote10
    Commented Feb 20, 2021 at 14:32

Yes and No - Depends how you use it.

Cookies if used to maintain client state at the client, for the client, of the client and by the client then they are restful.

If you are storing server state into the cookie then you are basically just shifting the load to the client - which isn't restful.

So what are some examples?


  • Authentication details or 'is logged in' kinda stuff
  • last viewed page or place in application etc.

Not Restful:

  • Storing session information

Restfulness comes from statelessness - of the server. Clients can maintain application state and send it to the server to say where they are so that the server can decide where to go from there. Basically sessions/states need historical data and are dependent on past requests so to speak, restful applications ideally aren't (It's not viable to have a 100% pure restful application if you are going to have a login screen :)

  • 18
    If you store an "isLoggedIn" flag on the client, you might as well use no authentication at all.
    – tdammers
    Commented Mar 23, 2012 at 6:54
  • This definitely makes sense - storing application state client-side wouldn't be consistent with REST, but client information that it uses to represent itself seems fine. Commented Mar 26, 2012 at 14:15
  • 1
    I'd like to add that putting authentication information in cookies leaves open the possibility of cross-site request forgery attacks. There are better ways, I suggest copying Amazon: docs.aws.amazon.com/AmazonS3/latest/API/… Commented Jun 16, 2014 at 18:11
  • 1
    @tdammers what about if the "isLoggedIn" flag is in a JWT? Then that should be secure, providing the JWT is issued and verified properly. Commented Aug 26, 2017 at 18:34
  • 1
    @AaronJSpetner: Do not use JWT for sessions.
    – tdammers
    Commented Sep 1, 2017 at 17:59

One can use cookies. REST allows them.

REST requires that any session information be stored on the client side, but when it comes to authentication, some information has to stay on the server side for security reasons.

From one of my blog posts, there is a general agreement that authentication data is considered out of scope regarding REST. Hence, it is ok for servers to keep some of this session data on their side.

  • REST is statelessness. restfulapi.net/statelessness It says "For becoming stateless, do not store even authentication/authorization details of client. Provide credentials with the request. Each request MUST stand alone and should not be affected by the previous conversation happened from the same client in past." Commented Feb 4, 2021 at 6:26
  • 1
    No, REST does not allow cookies, because a) they are independent of application state; b) they have no defined semantics, cf. § Cookies of Roy Fielding’s thesis.
    – Géry Ogam
    Commented May 22, 2021 at 23:00
  • @AleksandrRyabov If a cookie is containing an encrypted claims token with the user ID, it is doing the job of passing the credentials with the request. It's taking the place of the Authorization header.
    – Jez
    Commented Mar 24, 2023 at 19:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.