Project

General

Profile

Actions

Feature #42592

closed

FE sessions (cookies) should only be created when needed

Added by Stefan Neufeind about 12 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
Start date:
2012-11-01
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
hard
Sprint Focus:

Description

Currently on every request, if not already present, a FE-session-cookie is set for the user. Imho this could/should be avoided until needed - for example until data is written into the session.

(PS: If there are arguments against this as a general solution, maybe it could at least be configurable.)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #53598: Select/Delete fe_sessions twice per requestClosedAlexander Opitz2013-11-13

Actions
Actions #1

Updated by Stefan Neufeind about 12 years ago

Steffen Müller agreed but suggested to first write some testcases and refactor the code in question.

Actions #2

Updated by Thorsten Kahler about 12 years ago

  • Tracker changed from Bug to Feature
  • Category set to Frontend
  • Status changed from New to Accepted
  • Complexity set to hard

There are already some ways to work around it (see EXT:moc_varnish) but there should be a way to configure this in the core.

Actions #3

Updated by Mathias Schreiber almost 10 years ago

  • Target version set to 7.2 (Frontend)
Actions #4

Updated by Christian Kuhn almost 10 years ago

  • Status changed from Accepted to Resolved

It is possible since 6.2 (?) to have no FE cookies set.

Actions #5

Updated by Stefan Neufeind almost 10 years ago

Yes resolved in 6.2 (or so). This issue dates back to stone-age (well, event 4.5) :-) Thanks for finding/closing.

Actions #6

Updated by Riccardo De Contardi about 7 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF