---
title: "Discussion on \"Understanding Web Authentication: Sessions vs. Tokens\" | Hashnode"
description: "Discussion on \"Understanding Web Authentication: Sessions vs. Tokens\". When we build web applications, we face a fundamental technical hurdle: HTTP is a stateless protocol. This means every time a user requests a new page or clicks a link, the server treats that request"
url: "https://hashnode.com/posts/understanding-web-authentication-sessions-vs-tokens/6a00b3c4e3eebc2e20a22dd4"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Understanding Web Authentication: Sessions vs. Tokens](https://srujanee-chaicode-webdev-blogs.hashnode.dev/understanding-web-authentication-sessions-vs-tokens?utm_source=hashnode&utm_medium=feed)

When we build web applications, we face a fundamental technical hurdle: HTTP is a stateless protocol. This means every time a user requests a new page or clicks a link, the server treats that request

May 10 · 5 min read · srujanee-chaicode-webdev-blogs.hashnode.dev  
Read the article

-   [#chaicode](https://hashnode.com/tag/chaicode)
-   [#chaicode-webdev-cohort-2026](https://hashnode.com/tag/chaicode-webdev-cohort-2026)
-   [#authentication](https://hashnode.com/tag/authentication)
-   [#jwt](https://hashnode.com/tag/jwt)
-   [#session](https://hashnode.com/tag/session)

## Written by

[Srujanee Nayak](https://hashnode.com/@srujanee20)

@srujanee20

  
[View profile](https://hashnode.com/@srujanee20)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.