In Microsoft ASP.NET, when you use the Response.Addheader method to add a response header, the response header will always be encoded as UTF-8. You cannot specify an encoding type. For example, if you have the following code example in an ASP.NET page that contains some Korean characters in the file name, and you try to browse the page by using Microsoft Internet Explorer on a Korean version of Microsoft Windows, the Korean characters that are in the file name will appear as garbage in the File Download dialog box.

private void Page_Load(object sender, System.EventArgs e)

                {
                        string filename="<Some Korean Characters>.txt";

                        Response.ContentType = "text/plain";
                        Response.Clear(); 
                        byte[] buffer={65}; 
                        Response.AddHeader("Content-Disposition","attachment;filename="+filename); 
                        Response.BinaryWrite(buffer);
                        Response.Flush();
                        Response.End();
            }

Back to the top

This problem occurs because the response header that is added by the Response.Addheader method is always encoded as UTF-8 in ASP.NET.

Back to the top

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework 1.1 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

The Microsoft .NET Framework 1.1 Service Pack 1 (SP1)

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version        Size       File name
   --------------------------------------------------------------
   14-Apr-2005  02:08  1.1.4322.2315    258,048  Aspnet_isapi.dll  
   14-Apr-2005  02:08  1.1.4322.2315     32,768  Aspnet_wp.exe    
   14-Apr-2005  01:15  1.1.4322.2315  1,261,568  System.web.dll   

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

After you apply this hotfix, an additional responseHeaderEncoding attribute is available in the <globalization> element in the Web.config file. This new attribute lets you explicitly specify the response header encoding. To specify the response header encoding as Korean, add the attribute by using the following code example:

<globalization 
           responseHeaderEncoding="korean"
   />

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top