Tin Tuc Viet Nam - Vietnam news, Asia news and World news ...

saigonbao.com
  • Domain Name
    saigonbao.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #32407
  • Page Size
    208.6 KB
  • Ip Address
    66.55.88.60
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 14 JPG, 6 PNG

Website Meta Analysis

  • Title
    SaigonBao.com - Tin Tuc Viet Nam - Vietnam News
  • Meta Keyword
    saigon,saigonbao,saigon bao,vietnam,viet,hanoi,tin,tuc,news,asia,asia pacific,south east asia,money,investing,stock,market,exchange,currency,fx,forex,dollars,yen,euro,wall street,index,bond,mutual fund,standard and poor's
  • Meta Description
    Tin Tuc Viet Nam - Vietnam news, Asia news and World news

Technical Analysis

  • Webserver
    Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • Ip Address
    66.55.88.60
  • Domain Age
    14 Years, 1 Months, 24 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from saigonbao.com.

HTML Analysis

  • date: Thu, 25 Jul 2013 07:03:07 GMT
  • server: Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • last-modified: Fri, 19 Jul 2013 21:47:22 GMT
  • etag: "c400b-356d6-4e1e445854e80"
  • accept-ranges: bytes
  • content-length: 218838
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Ngo Huynh, Mai Thao
ATTN SAIGONBAO.COM
care of Network Solutions
PO Box 459
Drums, PA. US 18222


Domain Name: SAIGONBAO.COM



Administrative Contact, Technical Contact:
Ngo Huynh, Mai Thao email
ATTN SAIGONBAO.COM
care of Network Solutions
PO Box 459
Drums, PA 18222
US
570-708-8780


Record expires on 15-Jun-2019.
Record created on 23-Sep-2011.
Database last updated on 30-Sep-2012 23:28:19 EDT.

Domain servers in listed order:

NS1.SAIGONBAO.COM 66.55.88.60
NS2.SAIGONBAO.COM 66.55.89.128

DNS Analysis


DNS servers
ns1.saigonbao.com [66.55.88.60]
ns2.saigonbao.com [66.55.89.128]


DNS Records

Answer records
saigonbao.com MX
preference: 0
exchange: saigonbao.com
14400s
saigonbao.com SOA
server: ns1.saigonbao.com
email: huynhquangthanh@gmail.com
serial: 2011102402
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
saigonbao.com NS  ns2.saigonbao.com 86400s
saigonbao.com NS  ns1.saigonbao.com 86400s
saigonbao.com A 66.55.88.60 14400s

Authority records

Additional records
saigonbao.com A 66.55.88.60 14400s

IP 66.55.88.60 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 66.55.88.60

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 31 Errors
  • 32 Warnings
Ratio Text/Html
  • 0.7379473376243417
Message Error
  • Error Line 3, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <script language=javascript>if((navigator.userAgent.match(/iPhone/i)) || (navig…
  • Error Line 3, Column 28: required attribute "type" not specified
    <script language=javascript>if((navigator.userAgent.match(/iPhone/i)) || (navig…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 91, Column 30: there is no attribute "height"
      <table width="100%" height="86" border="0" align="center" cellpadding="0" cel…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 94, Column 154: cannot generate system identifier for general entity "u"
    …ijit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></scrip…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 94, Column 154: general entity "u" not defined and no default entity
    …ijit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></scrip…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 94, Column 155: reference not terminated by REFC delimiter
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 94, Column 155: reference to external entity in attribute value
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 94, Column 155: reference to entity "u" for which no system identifier could be generated
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 94, Column 153: entity was defined here
    …lijit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></scri…
  • Warning Line 94, Column 166: cannot generate system identifier for general entity "width"
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 94, Column 166: general entity "width" not defined and no default entity
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 94, Column 171: reference not terminated by REFC delimiter
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 94, Column 171: reference to external entity in attribute value
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 94, Column 171: reference to entity "width" for which no system identifier could be generated
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 94, Column 165: entity was defined here
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>
  • Warning Line 94, Column 176: cannot generate system identifier for general entity "height"
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 94, Column 176: general entity "height" not defined and no default entity
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 94, Column 182: reference not terminated by REFC delimiter
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 94, Column 182: reference to external entity in attribute value
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 94, Column 182: reference to entity "height" for which no system identifier could be generated
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 94, Column 175: entity was defined here
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>
  • Warning Line 389, Column 82: cannot generate system identifier for general entity "z"
    …rc="http://www.lijit.com/delivery/fp?u=saigonbao&z=190235"></script>&nbsp;</td>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 389, Column 82: general entity "z" not defined and no default entity
    …rc="http://www.lijit.com/delivery/fp?u=saigonbao&z=190235"></script>&nbsp;</td>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 389, Column 83: reference not terminated by REFC delimiter
    …rc="http://www.lijit.com/delivery/fp?u=saigonbao&z=190235"></script>&nbsp;</td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 389, Column 83: reference to external entity in attribute value
    …rc="http://www.lijit.com/delivery/fp?u=saigonbao&z=190235"></script>&nbsp;</td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 389, Column 83: reference to entity "z" for which no system identifier could be generated
    …rc="http://www.lijit.com/delivery/fp?u=saigonbao&z=190235"></script>&nbsp;</td>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 389, Column 81: entity was defined here
    …rc="http://www.lijit.com/delivery/fp?u=saigonbao&z=190235"></script>&nbsp;</td>
  • Error Line 418, Column 89: required attribute "alt" not specified
    …<area shape="rect" coords="671,3,728,16" href="industry/index-industry.html" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 419, Column 84: required attribute "alt" not specified
    …     <area shape="rect" coords="619,3,665,17" href="newsasia/francenews.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 420, Column 84: required attribute "alt" not specified
    …     <area shape="rect" coords="557,3,608,18" href="newsasia/europenews.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 421, Column 84: required attribute "alt" not specified
    …     <area shape="rect" coords="494,4,551,17" href="technology/military.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 422, Column 75: required attribute "alt" not specified
              <area shape="rect" coords="414,3,486,16" href="thegioi-1.html" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 423, Column 83: required attribute "alt" not specified
    …      <area shape="rect" coords="361,3,402,18" href="newsasia/chinanews.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 424, Column 92: required attribute "alt" not specified
    …ea shape="rect" coords="303,4,353,17" href="http://www.dailynewscanada.com/" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 425, Column 86: required attribute "alt" not specified
    …   <area shape="rect" coords="229,3,290,15" href="california/california.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 426, Column 73: required attribute "alt" not specified
              <area shape="rect" coords="159,4,216,17" href="business.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 427, Column 82: required attribute "alt" not specified
    …       <area shape="rect" coords="4,4,76,17" href="newsasia/asiapacific.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 428, Column 86: required attribute "alt" not specified
    …   <area shape="rect" coords="88,4,145,17" href="newsasia/australianews.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 434, Column 79: required attribute "alt" not specified
              <area shape="rect" coords="631,3,720,16" href="world-map-news.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 435, Column 84: required attribute "alt" not specified
    …     <area shape="rect" coords="538,3,619,15" href="newsasia/uspolitics.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 436, Column 84: required attribute "alt" not specified
    …     <area shape="rect" coords="452,3,524,16" href="newsasia/topstories.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 437, Column 81: required attribute "alt" not specified
    …        <area shape="rect" coords="363,3,435,16" href="technology/index.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 438, Column 84: required attribute "alt" not specified
    …     <area shape="rect" coords="290,3,349,16" href="newsasia/seasianews.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 439, Column 83: required attribute "alt" not specified
    …      <area shape="rect" coords="225,2,279,16" href="technology/science.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 440, Column 84: required attribute "alt" not specified
    …     <area shape="rect" coords="169,4,213,16" href="newsasia/russianews.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 441, Column 80: required attribute "alt" not specified
              <area shape="rect" coords="84,3,159,15" href="newsasia/mideast.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 442, Column 82: required attribute "alt" not specified
    …       <area shape="rect" coords="14,3,73,14" href="future/fashion news.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 448, Column 113: required attribute "alt" not specified
    …s="602,3,688,15" href="viet-nam-tong-quat/nong-nghiep/index-nong-nghiep.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 449, Column 112: required attribute "alt" not specified
    …ds="515,4,593,16" href="viet-nam-tong-quat/ngu-nghiep/index-ngu-nghiep.html" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 450, Column 71: required attribute "alt" not specified
              <area shape="rect" coords="429,3,507,17" href="TVN-NG.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 451, Column 82: required attribute "alt" not specified
    …       <area shape="rect" coords="340,3,421,16" href="nang-luong-energy.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 452, Column 77: required attribute "alt" not specified
              <area shape="rect" coords="271,3,329,16" href="TVN-ky-thuat.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 453, Column 71: required attribute "alt" not specified
              <area shape="rect" coords="205,3,262,15" href="TVN-KT.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 454, Column 113: required attribute "alt" not specified
    …s="113,3,197,16" href="viet-nam-tong-quat/cong-nghiep/index-cong-nghiep.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 455, Column 81: required attribute "alt" not specified
    …        <area shape="rect" coords="35,3,101,16" href="newsasia/vietnews.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 461, Column 87: required attribute "alt" not specified
    …  <area shape="rect" coords="584,2,679,16" href="newsasia/vietnam-news.html" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 462, Column 80: required attribute "alt" not specified
              <area shape="rect" coords="494,2,576,18" href="bao-chi-noi-dia.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 463, Column 94: required attribute "alt" not specified
    … shape="rect" coords="395,2,487,18" href="news-room-cong-san/vn-express.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 464, Column 83: required attribute "alt" not specified
    …      <area shape="rect" coords="301,2,388,17" href="news-room-chdc/rfa.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 465, Column 71: required attribute "alt" not specified
              <area shape="rect" coords="209,0,289,18" href="TVN-TM.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 466, Column 71: required attribute "alt" not specified
              <area shape="rect" coords="118,2,199,17" href="TVN-QS.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 467, Column 71: required attribute "alt" not specified
              <area shape="rect" coords="48,2,106,18" href="vietnam.htm" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 2477, Column 20: required attribute "type" not specified
                <script>   

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 2480, Column 10: character "<" is the first character of a delimiter but occurred as data
    if (year < 1000)   

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 2485, Column 9: character "<" is the first character of a delimiter but occurred as data
    if (daym<10)   

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 2489, Column 85: document type does not allow element "font" here
    … face='Arial, Tahoma, Times New Roman'>"+dayarray[day]+", ng&#224;y "+daym+" "…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 2516, Column 130: reference not terminated by REFC delimiter
    …jit.com/www/delivery/fpi.js?z=190879&u=saigonbao&width=160&height=600"></scrip…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2516, Column 130: reference to external entity in attribute value
    …jit.com/www/delivery/fpi.js?z=190879&u=saigonbao&width=160&height=600"></scrip…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2516, Column 130: reference to entity "u" for which no system identifier could be generated
    …jit.com/www/delivery/fpi.js?z=190879&u=saigonbao&width=160&height=600"></scrip…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 94, Column 153: entity was defined here
    …lijit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></scri…
  • Warning Line 2516, Column 146: reference not terminated by REFC delimiter
    …delivery/fpi.js?z=190879&u=saigonbao&width=160&height=600"></script>&nbsp;</td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2516, Column 146: reference to external entity in attribute value
    …delivery/fpi.js?z=190879&u=saigonbao&width=160&height=600"></script>&nbsp;</td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2516, Column 146: reference to entity "width" for which no system identifier could be generated
    …delivery/fpi.js?z=190879&u=saigonbao&width=160&height=600"></script>&nbsp;</td>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 94, Column 165: entity was defined here
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>
  • Warning Line 2516, Column 157: reference not terminated by REFC delimiter
    …delivery/fpi.js?z=190879&u=saigonbao&width=160&height=600"></script>&nbsp;</td>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2516, Column 157: reference to external entity in attribute value
    …delivery/fpi.js?z=190879&u=saigonbao&width=160&height=600"></script>&nbsp;</td>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2516, Column 157: reference to entity "height" for which no system identifier could be generated
    …delivery/fpi.js?z=190879&u=saigonbao&width=160&height=600"></script>&nbsp;</td>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 94, Column 175: entity was defined here
    …jit.com/www/delivery/fpi.js?z=191008&u=saigonbao&width=728&height=90"></script>
  • Warning Line 2538, Column 81: cannot generate system identifier for general entity "o"
    …://rcm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=1…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2538, Column 81: general entity "o" not defined and no default entity
    …://rcm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=1…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 2538, Column 82: reference not terminated by REFC delimiter
    …//rcm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2538, Column 82: reference to external entity in attribute value
    …//rcm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2538, Column 82: reference to entity "o" for which no system identifier could be generated
    …//rcm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 80: entity was defined here
    …p://rcm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=…
  • Warning Line 2538, Column 85: cannot generate system identifier for general entity "p"
    …cm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2538, Column 85: general entity "p" not defined and no default entity
    …cm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 2538, Column 86: reference not terminated by REFC delimiter
    …m.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=139008…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2538, Column 86: reference to external entity in attribute value
    …m.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=139008…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2538, Column 86: reference to entity "p" for which no system identifier could be generated
    …m.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=139008…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 84: entity was defined here
    …rcm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=1390…
  • Warning Line 2538, Column 90: cannot generate system identifier for general entity "l"
    …azon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&f…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2538, Column 90: general entity "l" not defined and no default entity
    …azon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&f…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 2538, Column 91: reference not terminated by REFC delimiter
    …zon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2538, Column 91: reference to external entity in attribute value
    …zon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2538, Column 91: reference to entity "l" for which no system identifier could be generated
    …zon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 89: entity was defined here
    …mazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&…
  • Warning Line 2538, Column 96: cannot generate system identifier for general entity "mode"
    …om/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=000…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2538, Column 96: general entity "mode" not defined and no default entity
    …om/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=000…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 2538, Column 100: reference not terminated by REFC delimiter
    …/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=000000&…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2538, Column 100: reference to external entity in attribute value
    …/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=000000&…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2538, Column 100: reference to entity "mode" for which no system identifier could be generated
    …/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=000000&…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 95: entity was defined here
    …com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=00…
  • Warning Line 2538, Column 113: cannot generate system identifier for general entity "browse"
    …aocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2538, Column 113: general entity "browse" not defined and no default entity
    …aocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 2538, Column 119: reference not terminated by REFC delimiter
    …o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2538, Column 119: reference to external entity in attribute value
    …o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2538, Column 119: reference to entity "browse" for which no system identifier could be generated
    …o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 112: entity was defined here
    …baocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&l…
  • Warning Line 2538, Column 129: cannot generate system identifier for general entity "fc1"
    …=bn1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFF…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2538, Column 129: general entity "fc1" not defined and no default entity
    …=bn1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFF…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 2538, Column 132: reference not terminated by REFC delimiter
    …1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2538, Column 132: reference to external entity in attribute value
    …1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2538, Column 132: reference to entity "fc1" for which no system identifier could be generated
    …1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 128: entity was defined here
    …l=bn1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FF…
  • Warning Line 2538, Column 140: cannot generate system identifier for general entity "lt1"
    …c-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" …

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2538, Column 140: general entity "lt1" not defined and no default entity
    …c-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" …

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 2538, Column 143: reference not terminated by REFC delimiter
    …ardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" mar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2538, Column 143: reference to external entity in attribute value
    …ardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" mar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2538, Column 143: reference to entity "lt1" for which no system identifier could be generated
    …ardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" mar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 139: entity was defined here
    …pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr"…
  • Warning Line 2538, Column 151: cannot generate system identifier for general entity "lc1"
    …browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2538, Column 151: general entity "lc1" not defined and no default entity
    …browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 2538, Column 154: reference not terminated by REFC delimiter
    …wse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2538, Column 154: reference to external entity in attribute value
    …wse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2538, Column 154: reference to entity "lc1" for which no system identifier could be generated
    …wse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 150: entity was defined here
    …&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidt…
  • Warning Line 2538, Column 162: cannot generate system identifier for general entity "bg1"
    …0871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" margin…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2538, Column 162: general entity "bg1" not defined and no default entity
    …0871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" margin…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 2538, Column 165: reference not terminated by REFC delimiter
    …1&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginhei…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2538, Column 165: reference to external entity in attribute value
    …1&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginhei…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2538, Column 165: reference to entity "bg1" for which no system identifier could be generated
    …1&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginhei…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 161: entity was defined here
    …00871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" margi…
  • Warning Line 2538, Column 173: cannot generate system identifier for general entity "f"
    …0000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0" …

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 2538, Column 173: general entity "f" not defined and no default entity
    …0000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0" …

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 2538, Column 174: reference not terminated by REFC delimiter
    …000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0" w…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2538, Column 174: reference to external entity in attribute value
    …000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0" w…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2538, Column 174: reference to entity "f" for which no system identifier could be generated
    …000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0" w…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 172: entity was defined here
    …00000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0"…
  • Error Line 2538, Column 245: there is no attribute "border"
    …t="0" width="160" height="600" border="0" frameborder="0" style="border:none;"…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 2542, Column 82: reference not terminated by REFC delimiter
    …//rcm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=wireless-phones&brows…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2542, Column 82: reference to external entity in attribute value
    …//rcm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=wireless-phones&brows…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2542, Column 82: reference to entity "o" for which no system identifier could be generated
    …//rcm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=wireless-phones&brows…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 80: entity was defined here
    …p://rcm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=…
  • Warning Line 2542, Column 86: reference not terminated by REFC delimiter
    …m.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=wireless-phones&browse=23…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2542, Column 86: reference to external entity in attribute value
    …m.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=wireless-phones&browse=23…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2542, Column 86: reference to entity "p" for which no system identifier could be generated
    …m.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=wireless-phones&browse=23…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 84: entity was defined here
    …rcm.amazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=1390…
  • Warning Line 2542, Column 91: reference not terminated by REFC delimiter
    …zon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=wireless-phones&browse=2335752…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2542, Column 91: reference to external entity in attribute value
    …zon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=wireless-phones&browse=2335752…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2542, Column 91: reference to entity "l" for which no system identifier could be generated
    …zon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=wireless-phones&browse=2335752…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 89: entity was defined here
    …mazon.com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&…
  • Warning Line 2542, Column 100: reference not terminated by REFC delimiter
    …/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=wireless-phones&browse=2335752011&fc1=0…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2542, Column 100: reference to external entity in attribute value
    …/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=wireless-phones&browse=2335752011&fc1=0…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2542, Column 100: reference to entity "mode" for which no system identifier could be generated
    …/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=wireless-phones&browse=2335752011&fc1=0…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 95: entity was defined here
    …com/e/cm?t=saigonbaocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=00…
  • Warning Line 2542, Column 123: reference not terminated by REFC delimiter
    …p=14&l=bn1&mode=wireless-phones&browse=2335752011&fc1=000000&lt1=_blank&lc1=33…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2542, Column 123: reference to external entity in attribute value
    …p=14&l=bn1&mode=wireless-phones&browse=2335752011&fc1=000000&lt1=_blank&lc1=33…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2542, Column 123: reference to entity "browse" for which no system identifier could be generated
    …p=14&l=bn1&mode=wireless-phones&browse=2335752011&fc1=000000&lt1=_blank&lc1=33…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 112: entity was defined here
    …baocom&o=1&p=14&l=bn1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&l…
  • Warning Line 2542, Column 138: reference not terminated by REFC delimiter
    …=wireless-phones&browse=2335752011&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2542, Column 138: reference to external entity in attribute value
    …=wireless-phones&browse=2335752011&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2542, Column 138: reference to entity "fc1" for which no system identifier could be generated
    …=wireless-phones&browse=2335752011&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 128: entity was defined here
    …l=bn1&mode=pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FF…
  • Warning Line 2542, Column 149: reference not terminated by REFC delimiter
    …hones&browse=2335752011&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" mar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2542, Column 149: reference to external entity in attribute value
    …hones&browse=2335752011&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" mar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2542, Column 149: reference to entity "lt1" for which no system identifier could be generated
    …hones&browse=2335752011&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" mar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 139: entity was defined here
    …pc-hardware&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr"…
  • Warning Line 2542, Column 160: reference not terminated by REFC delimiter
    …e=2335752011&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2542, Column 160: reference to external entity in attribute value
    …e=2335752011&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2542, Column 160: reference to entity "lc1" for which no system identifier could be generated
    …e=2335752011&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 150: entity was defined here
    …&browse=13900871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidt…
  • Warning Line 2542, Column 171: reference not terminated by REFC delimiter
    …1&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginhei…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2542, Column 171: reference to external entity in attribute value
    …1&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginhei…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2542, Column 171: reference to entity "bg1" for which no system identifier could be generated
    …1&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginhei…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 161: entity was defined here
    …00871&fc1=000000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" margi…
  • Warning Line 2542, Column 180: reference not terminated by REFC delimiter
    …000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0" w…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 2542, Column 180: reference to external entity in attribute value
    …000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0" w…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 2542, Column 180: reference to entity "f" for which no system identifier could be generated
    …000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0" w…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 2538, Column 172: entity was defined here
    …00000&lt1=_blank&lc1=3366FF&bg1=FFFFFF&f=ifr" marginwidth="0" marginheight="0"…

Visitor Analysis

Daily Visitor
  • 5.017 visits