Magento with Nginx and Varnish - 302's, cookies, and redirects?

Magento with Nginx and Varnish - 302's, cookies, and redirects?

August 23, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento with Nginx and Varnish - 302's, cookies, and redirects?

Title: Solving Magento Varnish Caching Issues with Nginx & Redirects

Introduction

Varnish is an excellent tool for caching static assets and improving the performance of your Magento e-commerce site. However, you may encounter issues related to redirects and cookies that can disrupt the caching process. In this post, we will explore a common problem where Magento redirects to the homepage after adding products to the cart or comparing items, causing Varnish to fail.

The Problem

When using Varnish for caching with your Magento site, you might face scenarios where certain actions don’t behave as expected. One such issue is when trying to add a product to the shopping cart or compare products. In these cases, instead of staying on the same page, the user is redirected to the homepage after completing the action.

This redirection causes Varnish to receive a 302 status code, which triggers it to return control back to the backend server (Nginx and PHP), breaking the caching process. The site ends up serving static content for some requests while handling dynamic content for others, leading to poor performance and inconsistent user experiences.

Understanding the Cause

The root cause of this issue lies in how Magento manages sessions and redirects after performing certain actions like adding products to the cart or comparison lists. When these actions are executed, Magento sets a session cookie and sends a 302 redirect to update the URL with the session ID appended as a query parameter.

Varnish, by default, doesn’t cache responses containing cookies or query parameters. As a result, when it receives a 302 redirect with a session cookie and query parameter, Varnish can’t cache it effectively, leading to the described behavior.

Solving the Issue

To resolve this problem, we need to make adjustments in both Nginx and Varnish configurations to ensure proper handling of redirects and cookies. Let’s go through each step:

Step 1: Configure Nginx

First, update your Nginx configuration file (usually located at /etc/nginx/nginx.conf) to handle Magento’s session management more effectively.

Add the following lines under the server block responsible for serving your Magento site:

location / {
    try_files $uri $uri/ /index.php?$args;
}

location ~ \.php$ {
    fastcgi_pass unix:/var/run/php-fpm.sock;
    fastcgi_index index.php;
    include fastcgi_params;

    # Add the following lines
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    fastcgi_param HTTPS off;
}

The try_files directive ensures that Nginx attempts to serve static files before passing requests to PHP. The fastcgi_param SCRIPT_FILENAME line helps PHP determine the correct script file path, which is crucial for session management.

Step 2: Adjust Varnish Configuration

Next, update your default VCL (Varnish configuration language) file located at /etc/varnish/default.vcl.

Modify the vcl_recv function as follows:

sub vcl_recv {
    # ...
    if (req.request == "GET" || req.request == "HEAD") {
        set req.http.Cookie = regsuball(req.http.Cookie, "(^|; )+session_id.*?;?", "");
        unset req.http.Cookie;
    }
    # ...

    if (req.url ~ "^/(media|js|skin)/.*\.(png|jpg|jpeg|gif|css|js|swf|ico)$") {
        # ...
    } else {
        set req.http.X-Origin-Server = "Nginx";
        # ...
    }

    # ...

    return (lookup);
}

In the modified vcl_recv function:

  1. We remove any session cookies (session_id) from incoming requests using regular expressions.
  2. For non-static file requests, we set the X-Origin-Server header to “Nginx” to help differentiate between static and dynamic content in Varnish.

Step 3: Restart Services

After making these changes, restart both Nginx and Varnish services for the updates to take effect:

sudo systemctl restart nginx
sudo systemctl restart varnish

Conclusion

By following the steps outlined above, you should now be able to resolve the Magento redirection issue that disrupts Varnish caching when adding products to the cart or comparing items. The modified Nginx configuration ensures proper handling of session management and redirects, while the updated Varnish VCL removes unnecessary cookies and differentiates between static and dynamic content.

Remember to always backup your configurations before making any changes and test thoroughly after applying updates to ensure smooth operation of your e-commerce site.

For more information on optimizing Magento performance with Varnish and Nginx, feel free to explore other resources at Laravel Company.

Happy caching!

Checkout Catalog Cache Performance

Our network