. NET message Request escaping

In. NET-related Web services messages, we often have some <requestXML>string</requestXML> requests that typically need to be escaped first, LoadRunner to recognize its meaning.

The following is a description of commonly used character escapes:

< in HTML, >,& has a special meaning, (the first two characters for the link sign,& for escaping), cannot be used directly, when using these three characters, should use their escape sequence. The escape sequence for & is &amp; or & #38;< escape sequence is &lt; & #60;> escape sequence is &gt; & #62; The former is a character escape sequence, and the latter is a sequence of numbers.

such as &lt; Font &gt; is displayed as <font>, and if written directly it is considered a link sign. It should be stated that:

A. There can be no spaces between the characters of the escape sequence;

B. The escape sequence must be ";" End

C. Individual & is not considered to be an escape start;

D. Case-sensitive, another character to be escaped is the double quotation mark "", its escape sequence is &quot; or & #34;

This article is from the "one step, one step" blog, please be sure to keep this source http://summerflowers.blog.51cto.com/5202033/1851062

. NET message Request escaping