iis - ASP.NET site move to IIS7 results in gibberish characters in page output -


I have an asp.net site that was running fine on Windows Server 2003 / IIS6.

I transferred it to Windows Server 2008 / IIS 7 and ASPX page output now includes Gibbertext Text. For example:

p

Most pages display properly, but here and there it is very easy I checked the event log and some Not even there.

Any thoughts that are going on here? How can I fix this?

I have noticed that when I add multiple servers, then this problem appears. Enter the statement in the aspx code:

   

The above .inc files contain only html, it appears that files should have a significant length to cause error. Here is the sample HTML I'm testing:

  & lt; Div class = "logo" & gt; & Lt; A href = "/" & gt; & Lt; Img src = "/ logo.png" alt = "logo" width = "31" height = "29" square = "logo" /> & Lt; / A & gt; & Lt; / Div & gt; & Lt; Div class = "logo" & gt; & Lt; A href = "/" & gt; & Lt; Img src = "/ logo.png" alt = "logo" width = "31" height = "29" square = "logo" /> & Lt; / A & gt; & Lt; / Div & gt; & Lt; Div class = "logo" & gt; & Lt; A href = "/" & gt; & Lt; Img src = "/ logo.png" alt = "logo" width = "31" height = "29" square = "logo" /> & Lt; / A & gt; & Lt; / Div & gt; & Lt; Div class = "logo" & gt; & Lt; A href = "/" & gt; & Lt; Img src = "/ logo.png" alt = "logo" width = "31" height = "29" square = "logo" /> & Lt; / A & gt; & Lt; / Div & gt; & Lt; Div class = "logo" & gt; & Lt; A href = "/" & gt; & Lt; Img src = "/ logo.png" alt = "logo" width = "31" height = "29" square = "logo" /> & Lt; / A & gt; & Lt; / Div & gt; & Lt; Div class = "logo" & gt; & Lt; A href = "/" & gt; & Lt; Img src = "/ logo.png" alt = "logo" width = "31" height = "29" square = "logo" /> & Lt; / A & gt; & Lt; / Div & gt; In addition to this, the vague characters look inconsistent if I change the ctrl + F5 pages, non-visible characters and sometimes do not appear at all.   

There is a discussion of a similar issue, I wonder if this is the problem you are seeing Here are the rocks. Scott has a quote from the answer:

If you want to answer the execution of the page after the answer, then answer. Type is set, then it will result in response to the response. Type and encoding set by the initial page - which may not be compatible with the characters on the second page Solution: Make sure that you are appropriately assigning the response type and the encoding on both pages.

Is it trying and trying to see that it works?

If that does not work, there is an interesting discussion on various configuration options, which you can try to implement continuous encoding on your site. You may want to use some of them; Additionally, she does not use MSDN article content type instructions but rather recommends it:

  & lt;% @ page request encoding = "UTF-8" response encoding = "UTF-8"%>  

It is not certain whether equivalent results will be generated as adjusting ContentType, but it is quite easy to try.


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -