• Hello

    Upon updating to WordPress 3.4.1, The “Cookie” header is no longer being added to the vary header which means a user cannot log in, comment or use any feature that requires cookies (unless of course if it’s already set).

    I have thoroughly checked web server configurations, checked all .htaccess files which revealed nothing to suspect. I’ve also tried cloned and subsequently installed new WordPress installations on blank databases (empty) on DreamHost, MediaTemple and an EC2 instance I was in the middle of deploying. I have checked through a few previous wp-login.php files from the archive that do not show any indication that it has been modified – this would obviously indicate it would be a problem my end unless I’ve missed something.

    I can use .htaccess to do ‘Header append Vary Cookie’, but that would also mean updating several hundred non multi-site websites, manually. Modifying wp-login.php to set the same header results in success but would also mean updating several hundred websites.

    Can anyone please shed some light on what’s going on or what else I can do to diagnose this issue? I must have missed something.

    Here’s one sites wp-config.php:

    <?php

    define(‘DB_NAME’, ‘*’);
    define(‘DB_USER’, ‘*’);
    define(‘DB_PASSWORD’, ‘*’);
    define(‘DB_HOST’, ‘*’);

    define(‘DB_CHARSET’, ‘utf8’);
    define(‘DB_COLLATE’, ‘utf8_unicode_ci’);

    define(‘AUTH_KEY’, ‘*’);
    define(‘SECURE_AUTH_KEY’, ‘*’);
    define(‘LOGGED_IN_KEY’, ‘*’);
    define(‘NONCE_KEY’, ‘*’);
    define(‘AUTH_SALT’, ‘*’);
    define(‘SECURE_AUTH_SALT’, ‘*’);
    define(‘LOGGED_IN_SALT’, ‘*’);
    define(‘NONCE_SALT’, ‘*’);

    $table_prefix = ‘*wp_’;

    define(‘WPLANG’, ‘en_GB’);

    define(‘WP_DEBUG’, false);

    define(‘WP_MEMORY_LIMIT’, ‘1024M’);

    /** Absolute path to the WordPress directory. */
    if ( !defined(‘ABSPATH’) )
    define(‘ABSPATH’, dirname(__FILE__) . ‘/’);

    /** Sets up WordPress vars and included files. */
    require_once(ABSPATH . ‘wp-settings.php’);

    ?>

  • The topic ‘Vary "Cookie" header not being set’ is closed to new replies.