When using CAS for unified authentication, use Western characters by default, localization is often required in actual use. At present, CAS is currently temporarily adopted as a unified authentication method for the platform, need to The page performs Chinese culture, so the CAS Server end page is re-written, and the coding of the JSP page is used in the page opening and using <% @ Page ContentType = ". However, in the actual access, Chinese have become ?? No issues for direct access to each page. What has led to this reason, it is originally the process of request forwarding in the process of requesting, which uses the default Western encoding, which adds statement response.set in the login.java DOGET function ("ContentType" "Text / html; charSet = GB2312"); problem can be successfully resolved.
