Why does my browser complain that cookies are not allowed when trying to access the Spam Quarantine?

Available Languages

Updated:August 12, 2014
Document ID:118276

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Question

Why does my browser complain that cookies are not allowed when trying to access the Spam Quarantine?

Symptoms

When you try to access the Spam Quarantine, you get the message "The form cannot be displayed in the browser because the use of session cookies has been disabled in the current browser settings. In order to load the form, session cookies must be allowed".

Environment

Cisco Email Security Appliance (ESA), Security Management Appliance (SMA), and all versions of AsyncOS.

First, check if cookies are disabled. On Internet Explorer, you can check this under Tools > Internet Options > Privacy > Advanced.

If cookies are enabled, this error may be caused by a hostname with an underscore character (_). This has been reported in Internet Explorer Versions 6 and 7.

The workaround is to either change the appliance hostname to not have underscore or to use the appliance IP address for accessing the GUI instead of the hostname.

Note: The underscore character is not valid in a hostname or a domain name, per RFC 952.

Revision History

Revision Publish Date Comments
1.0
12-Aug-2014
Initial Release
TAC Authored

Contributed by Cisco Engineers

  • Karl Young and Siddharth Rajpathak
    Cisco TAC Engineers.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products