You are browsing documentation for version 5.0 of OroCommerce, supported until January 2025. Read the documentation for version 6.0 (the latest LTS version) to get up-to-date information.

See our Release Process documentation for more information on the currently supported and upcoming releases.

Protect Cookies 

If the application is configured to be used via an SSL connection, you should protect the application cookies, too.

Cookies are protected with Secure and HttpOnly flags.

By default, all cookies used in ORO applications have the secure flag set to auto. This means cookies will have the secure flag for HTTPS requests and no such flag for HTTP requests.

Except for the CSRF cookie, all cookies have the httponly flag set to true. This means that the cookie will not be accessible by scripting languages, such as JavaScript.

More information about this configuration is available in the cookie secure configuration section of Symfony documentation.

If your application uses a proxy that redirects from https requests to http, the application will detect that the request was made with the http request. As a result, the auto value for the secure parameter will remove the secure flag.

In this case, you can manually set this parameter for each cookie via the configuration or reconfigure your web sever to add the secure flag by the server.

Reconfigure Apache Web Server 

To configure the Apache web server:

  • Enable in the Apache HTTP server configuration file;

  • In the configuration of your virtual domain, add:

    Header edit Set-Cookie ^(.*)$ $1;Secure
  • Restart the web server.