# Crosstalk in Django Sessions (Two browsers on One Device)

**URL:** <https://forum.djangoproject.com/t/crosstalk-in-django-sessions-two-browsers-on-one-device/44922>\
**Category:** Mystery Errors\
**Created:** [April 16, 2026, 4:02am UTC](https://forum.djangoproject.com/t/crosstalk-in-django-sessions-two-browsers-on-one-device/44922 "2026-04-16T04:02:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![onyeibo](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/onyeibo/32/11494_2.png) [@onyeibo](https://forum.djangoproject.com/u/onyeibo)\
**Post date:** [April 16, 2026, 4:02am UTC](https://forum.djangoproject.com/t/crosstalk-in-django-sessions-two-browsers-on-one-device/44922/1 "2026-04-16T04:02:28Z")

</div>

I am testing an app with two different browsers on my development machine. When I access the same page on the browsers, I notice that **browser-A** _(say Chrome)_ shows data that **browser-B** _(Firefox)_ just accessed a second ago despite the two browsers having different cookies. The URL for each instance is different which should facilitate fetching different data as per the values of the View `kwargs`. Yet, I see data belonging to **Browser-A** showing up in **Browser-B** … and sometimes, vice versa. The situation normalizes after a few refreshes. _Is this normal?_

So, I am wondering why this crosstalk is happening since the browsers are different. Is this because:

1. It is a development server?
2. The browsers are on the same machine, therefore they access same data? Shouldn’t one be able to access a cookie-based resource as User-A on browser-A, and User-B on Browser B on the same machine without crosstalks?
3. I am doing something wrong?

Please advise

---

<div class="post-metadata">

**Author:** ![onyeibo](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/onyeibo/32/11494_2.png) [@onyeibo](https://forum.djangoproject.com/u/onyeibo)\
**Post date:** [April 16, 2026, 7:22am UTC](https://forum.djangoproject.com/t/crosstalk-in-django-sessions-two-browsers-on-one-device/44922/2 "2026-04-16T07:22:36Z")

</div>

My bad.

I figured it out. Working with sessions is a delicate thing especially if one is updating views from GET and POST. With different user clients sending GET and POST requests randomly, one needs to be sure that forms are instantiating from the correct method.