Difference Between request.getSession() and request.getSession(true)

Last updated: January 16, 2024

Written by: baeldung

Reviewed by: David Martinez

Java Web

Servlet

Refactor Java code safely — and automatically — with OpenRewrite.

Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.

Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.

Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.

1. Overview

In this quick tutorial, we’ll see the difference between calling HttpServletRequest#getSession() and HttpServletRequest#getSession(boolean).

2. What’s the Difference?

The methods getSession() and getSession(boolean) are very similar. There’s a small difference, though. The difference is whether the session should be created if it doesn’t exist already.

Calling getSession() and getSession(true) are functionally the same: retrieve the current session, and if one doesn’t exist yet, create it.

Calling getSession(false), though, retrieves the current session, and if one doesn’t exist yet, returns null. Among other things, this is handy when we want to ask if the session exists.

3. Example

In this example, we are considering this scenario:

the user enters the user id and logs in to the application
the user then enters the user name and age and wants to update these details for the logged-in user

We’ll store the user values in the session to understand the usage of HttpServletRequest#getSession() and HttpServletRequest#getSession(boolean).

First, let’s create a servlet where we’re using HttpServletRequest#getSession() in its doGet() method:

protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
    HttpSession session = request.getSession();
    session.setAttribute("userId", request.getParameter("userId"));
}

At this point, the servlet will retrieve the existing session or create a new one for the logged-in user, if it doesn’t exist.

Next, we’ll set the userName attribute in the session.

As we want to update the details of the user for the respective user id, we want the same session and do not want to create a new session to store the user name.

So now, we will use HttpServletRequest#getSession(boolean) with false value:

protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
    HttpSession session = request.getSession(false);
    if (session != null) {
        session.setAttribute("userName", request.getParameter("userName"));
    }
}

This will result in setting the userName attribute on the same session that the userId was previously set.