Comparez les prix des billets d'avion et réserver un vol pas cher ! Recherchez un vol parmi 400 compagnies aériennes low cost et traditionnelles et profitez de tarifs avantageux avec Bravofly ! ...

bravofly.fr
  • Domain Name
    bravofly.fr
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #27007
  • Page Size
    66.1 KB
  • Ip Address
    62.212.75.138
  • Heading
    H1: 1, H2: 0, H3: 0, H4: 7, H5: 0, H6: 0
  • Images
    9 GIF, 0 JPG, 8 PNG

Website Meta Analysis

  • Title
    Vol pas cher Bravofly : billet d'avion pas cher, vol low cost
  • Meta Keyword
    vol pas cher, vol, vol low cost, vol au meilleur prix, promo vol, billets d'avion, billet d'avion pas cher, achat vol pas cher, achat billet d'avion, vol discount, vols dégriffés
  • Meta Description
    Comparez les prix des billets d'avion et réserver un vol pas cher ! Recherchez un vol parmi 400 compagnies aériennes low cost et traditionnelles et profitez de tarifs avantageux avec Bravofly !

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    62.212.75.138
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from bravofly.fr.

HTML Analysis

  • server: Apache
  • content-language: fr
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-type: text/html;charset=UTF-8
  • content-length: 14434
  • date: Thu, 28 Feb 2013 16:42:58 GMT
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
%%
%% This is the AFNIC Whois server.
%%
%% complete date format : DD/MM/YYYY
%% short date format : DD/MM
%% version : FRNIC-2.5
%%
%% Rights restricted by copyright.
%% See http://www.afnic.fr/afnic/web/mentions-legales-whois_en
%%
%% Use '-h' option to obtain more information about this service.
%%
%% [149.47.132.197 REQUEST] >> bravofly.fr
%%
%% RL Net [##########] - RL IP [#########.]
%%

domain: bravofly.fr
status: ACTIVE
hold: NO
holder-c: BS2017-FRNIC
admin-c: XB355-FRNIC
tech-c: ER507-FRNIC
zone-c: NFC1-FRNIC
nsl-id: NSL4892-FRNIC
registrar: EURODNS S.A.
anniversary: 30/07
created: 14/09/2005
last-update: 01/12/2011
source: FRNIC

ns-list: NSL4892-FRNIC
nserver: ns1.eurodns.com
nserver: ns2.eurodns.com
source: FRNIC

registrar: EURODNS S.A.
type: Isp Option 1
address: 2 rue Léon Laval
address: L-3372 LEUDELANGE
country: LU
phone: +352 27 37 25 1
fax-no: +352 27 27 37 25
e-mail: email
website: http://www.eurodns.com
anonymous: NO
registered: 24/09/2003
source: FRNIC

nic-hdl: ER507-FRNIC
type: ROLE
contact: EDNS ROLE
address: EuroDNS S.A.
address: 41, z.a. am Bann
address: 3372 Leudelange
address: LU
e-mail: email
admin-c: MM2096-FRNIC
tech-c: PYG1-FRNIC
changed: 15/05/2006 email
anonymous: NO
obsoleted: NO
source: FRNIC

nic-hdl: XB355-FRNIC
type: ROLE
contact: Xavier Buck
address: Eurodns France
address: 23-25, rue Jean Jacques Rousseau
address: 75001 Paris
country: FR
phone: +33 8 70 44 14 00
e-mail: email
admin-c: ER507-FRNIC
tech-c: ER507-FRNIC
changed: 21/09/2006 email
anonymous: NO
obsoleted: NO
source: FRNIC

nic-hdl: BS2017-FRNIC
type: ORGANIZATION
contact: Bravofly S.A.
address: Via Motta, 16
address: 6830 Chiasso
country: CH
phone: +352 263725200
e-mail: email
changed: 31/05/2010 email
anonymous: NO
obsoleted: NO
eligstatus: ok
eligdate: 01/06/2010 15:08:05
source: FRNIC

DNS Analysis


DNS servers
ns1.eurodns.com [80.92.65.2]
ns2.eurodns.com [80.92.89.242]


DNS Records

Answer records
bravofly.fr A 62.212.75.138 1800s
bravofly.fr MX
preference: 10
exchange: mfwd.eurodns.com
3600s
bravofly.fr SOA
server: ns1.eurodns.com
email: hostmaster@eurodns.com
serial: 2013010901
refresh: 86400
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
bravofly.fr NS  ns1.eurodns.com 86400s
bravofly.fr NS  ns2.eurodns.com 86400s

Authority records

Additional records

IP 62.212.75.138 Analysis

  • Country Code
    NL
  • Country Code3
    NLD
  • Country Name
    Netherlands
  • City
    Amsterdam
  • Continent Code
    EU
  • Latitude
    52.35
  • Longitude
    4.9167
  • No whois ip data for 62.212.75.138

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 111 Errors
  • 27 Warnings
Ratio Text/Html
  • 0.7156429616276836
Message Error
  • Warning Line 39, Column 71: NET-enabling start-tag requires SHORTTAG YES
          <link rel="canonical" href="http://www.bravofly.fr/vg1/vols.do" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 41, Column 53: document type does not allow element "META" here
        <meta http-equiv="Content-Language" content="fr">

    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).

  • Error Line 42, Column 70: document type does not allow element "META" here
        <meta http-equiv="content-type" content="text/html;charset=UTF-8">

    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).

  • Error Line 43, Column 38: document type does not allow element "META" here
        <meta name="Robots" content="all">

    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 46, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …  <link href="https://plus.google.com/110906309265283197601" rel="publisher" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 46, Column 80: document type does not allow element "LINK" here
    …  <link href="https://plus.google.com/110906309265283197601" rel="publisher" />

    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).

  • Error Line 50, Column 87: document type does not allow element "LINK" here
    …k rel="stylesheet" href="/vg1/css/commons.css" charset="UTF-8" type="text/css">

    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).

  • Error Line 51, Column 96: document type does not allow element "LINK" here
    …ylesheet" href="/vg1/css/fr/header-footer.css" charset="UTF-8" type="text/css">

    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).

  • Error Line 52, Column 98: document type does not allow element "LINK" here
    …esheet" type="text/css" href="/vg1/vs/v-3.3-46859-1/ve/bfwrobf/header2012.css">

    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).

  • Error Line 80, Column 9: end tag for element "HEAD" which is not open
      </head>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 81, Column 27: document type does not allow element "BODY" here
      <body class="volagratis">

    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).

  • Error Line 387, Column 43: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
        <div class="assist_number_full_height">0899 140 870</div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 388, Column 34: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
        <div class="assist_container">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 395, Column 34: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
        <div class="headphones_white"></div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 444, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_ar lang_icon"></div>Argentina

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 453, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_au lang_icon"></div>Australia

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 462, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_br lang_icon"></div>Brazil

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 471, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_ca lang_icon"></div>Canada

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 480, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_cn lang_icon"></div>China

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 489, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_cz lang_icon"></div>Czech Republic

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 498, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_dk lang_icon"></div>Denmark

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 507, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_de lang_icon"></div>Deutschland

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 516, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_es lang_icon"></div>Espa&ntilde;a

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 525, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_fr lang_icon"></div>France

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 534, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_gb lang_icon"></div>Great Britain

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 543, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_in lang_icon"></div>India

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 552, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_id lang_icon"></div>Indonesia

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 561, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_it lang_icon"></div>Italia

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 570, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_hu lang_icon"></div>Magyarorsz&aacute;g

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 579, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_my lang_icon"></div>Malaysia

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 588, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_mx lang_icon"></div>Mexico

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 597, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_no lang_icon"></div>Norway

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 606, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_at lang_icon"></div>&Ouml;sterreich

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 615, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_ph lang_icon"></div>Philippines

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 624, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_pl lang_icon"></div>Polska

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 633, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_pt lang_icon"></div>Portugal

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 642, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_ru lang_icon"></div>Россия

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 651, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_ro lang_icon"></div>Romania

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 660, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_ru lang_icon"></div>Russia

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 668, Column 140: cannot generate system identifier for general entity "resourcelist"
    …ontent/editor_buttons.jsp?action=show&resourcelist=&resource=%2Fsystem%2Fmodul…

    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 668, Column 140: general entity "resourcelist" not defined and no default entity
    …ontent/editor_buttons.jsp?action=show&resourcelist=&resource=%2Fsystem%2Fmodul…

    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.

  • Error Line 668, Column 152: reference to entity "resourcelist" for which no system identifier could be generated
    …r_buttons.jsp?action=show&resourcelist=&resource=%2Fsystem%2Fmodules%2Fit.head…

    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 668, Column 139: entity was defined here
    …content/editor_buttons.jsp?action=show&resourcelist=&resource=%2Fsystem%2Fmodu…
  • Warning Line 668, Column 154: cannot generate system identifier for general entity "resource"
    …buttons.jsp?action=show&resourcelist=&resource=%2Fsystem%2Fmodules%2Fit.header…

    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 668, Column 154: general entity "resource" not defined and no default entity
    …buttons.jsp?action=show&resourcelist=&resource=%2Fsystem%2Fmodules%2Fit.header…

    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.

  • Error Line 668, Column 162: reference to entity "resource" for which no system identifier could be generated
    …jsp?action=show&resourcelist=&resource=%2Fsystem%2Fmodules%2Fit.headermanager.…

    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 668, Column 153: entity was defined here
    …_buttons.jsp?action=show&resourcelist=&resource=%2Fsystem%2Fmodules%2Fit.heade…
  • Warning Line 668, Column 251: cannot generate system identifier for general entity "elementlanguage"
    …rces%2Fxsd_flags%2Fflags_flights.html&elementlanguage=en#vofly.ch" href="http:…

    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 668, Column 251: general entity "elementlanguage" not defined and no default entity
    …rces%2Fxsd_flags%2Fflags_flights.html&elementlanguage=en#vofly.ch" href="http:…

    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.

  • Error Line 668, Column 266: reference to entity "elementlanguage" for which no system identifier could be generated
    …s%2Fflags_flights.html&elementlanguage=en#vofly.ch" href="http://www.bravofly.…

    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 668, Column 250: entity was defined here
    …urces%2Fxsd_flags%2Fflags_flights.html&elementlanguage=en#vofly.ch" href="http…
  • Error Line 669, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_ch lang_icon"></div>Schweiz

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 678, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_sg lang_icon"></div>Singapore

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 687, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_za lang_icon"></div>South Africa

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 696, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_ch lang_icon"></div>Suisse

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 705, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_fi lang_icon"></div>Suomi

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 714, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_sv lang_icon"></div>Sverige

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 723, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_ch lang_icon"></div>Svizzera

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 732, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_th lang_icon"></div>Thailand

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 741, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_tr lang_icon"></div>T&uuml;rkiye

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 750, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_us lang_icon"></div>United States

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 759, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_vn lang_icon"></div>Vietnam

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 768, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_eu lang_icon"></div>Worldwide (English)

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 777, Column 39: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
            <div class="flag_uk lang_icon"></div>Україна

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 781, Column 21: document type does not allow element "DIV" here; assuming missing "LI" start-tag
    <div class="cleaner"></div>
  • Error Line 803, Column 118: document type does not allow element "LINK" here
    …" href="/vg1/vs/v-3.3-46859-1/ve/bfwrobf/css/fr/home.css" charset="ISO-8859-1">

    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).

  • Error Line 805, Column 104: document type does not allow element "LINK" here
    …type="text/css" href="/vg1/vs/v-3.3-46859-1/ve/bfwrobf/homepageComponents.css">

    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).

  • Error Line 822, Column 46: required attribute "ALT" not specified
          <img src="/images/vg_preno_hostess.gif">

    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 857, Column 83: cannot generate system identifier for general entity "href"
    ….com/plugins/likebox.php?locale=fr_FR&href=https%3A%2F%2Fwww.facebook.com%2FBr…

    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 857, Column 83: general entity "href" not defined and no default entity
    ….com/plugins/likebox.php?locale=fr_FR&href=https%3A%2F%2Fwww.facebook.com%2FBr…

    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.

  • Error Line 857, Column 87: reference to entity "href" for which no system identifier could be generated
    …/plugins/likebox.php?locale=fr_FR&href=https%3A%2F%2Fwww.facebook.com%2FBravof…

    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 857, Column 82: entity was defined here
    …k.com/plugins/likebox.php?locale=fr_FR&href=https%3A%2F%2Fwww.facebook.com%2FB…
  • Error Line 857, Column 369: there is no attribute "ALLOWTRANSPARENCY"
    … overflow:hidden; width:220px; height:60px;" allowTransparency="true"></iframe>

    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 929, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …hidden" id="search1_airports_hidden" name="search1_airports_hidden" value="" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 930, Column 89: NET-enabling start-tag requires SHORTTAG YES
    …input type="hidden" id="search1_focusctrl" name="search1_focusctrl" value="" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 931, Column 87: NET-enabling start-tag requires SHORTTAG YES
    … <input type="hidden" id="search1_keywords" name="search1_keywords" value="" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 932, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …hidden" id="search2_airports_hidden" name="search2_airports_hidden" value="" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 933, Column 88: NET-enabling start-tag requires SHORTTAG YES
    …<input type="hidden" id="search2_focusctrl" name="search2_focuctrl" value="" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 934, Column 87: NET-enabling start-tag requires SHORTTAG YES
    … <input type="hidden" id="search2_keywords" name="search2_keywords" value="" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 937, Column 36: ID "FILTER1" already defined
              <input type="hidden" id="filter1" name="filter1" value="TXT">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 936, Column 36: ID "FILTER1" first defined here
              <input type="hidden" id="filter1" name="filter1" value="TXT">
  • Warning Line 942, Column 71: NET-enabling start-tag requires SHORTTAG YES
              <input type="hidden" id="url" name="url" value="search3.do" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1072, Column 182: NET-enabling start-tag requires SHORTTAG YES
    …);"><img id="helpButtonAdults" class="helpButton" src="/images/info.png" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1072, Column 182: required attribute "ALT" not specified
    …);"><img id="helpButtonAdults" class="helpButton" src="/images/info.png" /></a>

    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 1110, Column 202: NET-enabling start-tag requires SHORTTAG YES
    …www3.staticroot.com/images/close.gif" width="11" height="11" alt="Close" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1118, Column 97: character ";" not allowed in attribute specification list
    …servation de groupe</span> <a href="#"; onclick="window.open('/vg1/others/popu…
  • Error Line 1143, Column 25: document type does not allow element "STYLE" here
      <style type="text/css">

    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 1166, Column 74: cannot generate system identifier for general entity "departureAirports"
    ….fr/vg1/pricesearchstatic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_s…

    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 1166, Column 74: general entity "departureAirports" not defined and no default entity
    ….fr/vg1/pricesearchstatic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_s…

    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.

  • Error Line 1166, Column 91: reference to entity "departureAirports" for which no system identifier could be generated
    …chstatic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandisi…

    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 1166, Column 73: entity was defined here
    …y.fr/vg1/pricesearchstatic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_…
  • Warning Line 1166, Column 97: cannot generate system identifier for general entity "maxPrice"
    …ic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&utm…

    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 1166, Column 97: general entity "maxPrice" not defined and no default entity
    …ic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&utm…

    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.

  • Error Line 1166, Column 105: reference to entity "maxPrice" for which no system identifier could be generated
    …n?sl=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&utm_campaig…

    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 1166, Column 96: entity was defined here
    …tic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&ut…
  • Warning Line 1166, Column 109: cannot generate system identifier for general entity "utm_source"
    …=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&utm_campaign=Ba…

    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 1166, Column 109: general entity "utm_source" not defined and no default entity
    …=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&utm_campaign=Ba…

    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.

  • Error Line 1166, Column 119: reference to entity "utm_source" for which no system identifier could be generated
    …reAirports=AFRA&maxPrice=50&utm_source=Merchandising&utm_campaign=Banner_HP&ut…

    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 1166, Column 108: entity was defined here
    …l=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&utm_campaign=B…
  • Warning Line 1166, Column 134: cannot generate system identifier for general entity "utm_campaign"
    …&maxPrice=50&utm_source=Merchandising&utm_campaign=Banner_HP&utm_medium=Price_…

    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 1166, Column 134: general entity "utm_campaign" not defined and no default entity
    …&maxPrice=50&utm_source=Merchandising&utm_campaign=Banner_HP&utm_medium=Price_…

    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.

  • Error Line 1166, Column 146: reference to entity "utm_campaign" for which no system identifier could be generated
    …&utm_source=Merchandising&utm_campaign=Banner_HP&utm_medium=Price_50" onclick=…

    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 1166, Column 133: entity was defined here
    …A&maxPrice=50&utm_source=Merchandising&utm_campaign=Banner_HP&utm_medium=Price…
  • Warning Line 1166, Column 157: cannot generate system identifier for general entity "utm_medium"
    …=Merchandising&utm_campaign=Banner_HP&utm_medium=Price_50" onclick="secondTrac…

    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 1166, Column 157: general entity "utm_medium" not defined and no default entity
    …=Merchandising&utm_campaign=Banner_HP&utm_medium=Price_50" onclick="secondTrac…

    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.

  • Error Line 1166, Column 167: reference to entity "utm_medium" for which no system identifier could be generated
    …sing&utm_campaign=Banner_HP&utm_medium=Price_50" onclick="secondTracker._track…

    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 1166, Column 156: entity was defined here
    …e=Merchandising&utm_campaign=Banner_HP&utm_medium=Price_50" onclick="secondTra…
  • Error Line 1166, Column 389: required attribute "ALT" not specified
    …0euro.png" width="150" height="100" border="0" style="display:block;"></a></td>

    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 1167, Column 91: reference to entity "departureAirports" for which no system identifier could be generated
    …chstatic.action?sl=1&departureAirports=AFRA&maxPrice=100&utm_source=Merchandis…

    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 1166, Column 73: entity was defined here
    …y.fr/vg1/pricesearchstatic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_…
  • Error Line 1167, Column 105: reference to entity "maxPrice" for which no system identifier could be generated
    …n?sl=1&departureAirports=AFRA&maxPrice=100&utm_source=Merchandising&utm_campai…

    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 1166, Column 96: entity was defined here
    …tic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&ut…
  • Error Line 1167, Column 120: reference to entity "utm_source" for which no system identifier could be generated
    …eAirports=AFRA&maxPrice=100&utm_source=Merchandising&utm_campaign=Banner_HP&ut…

    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 1166, Column 108: entity was defined here
    …l=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&utm_campaign=B…
  • Error Line 1167, Column 147: reference to entity "utm_campaign" for which no system identifier could be generated
    …&utm_source=Merchandising&utm_campaign=Banner_HP&utm_medium=Price_100" onclick…

    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 1166, Column 133: entity was defined here
    …A&maxPrice=50&utm_source=Merchandising&utm_campaign=Banner_HP&utm_medium=Price…
  • Error Line 1167, Column 168: reference to entity "utm_medium" for which no system identifier could be generated
    …sing&utm_campaign=Banner_HP&utm_medium=Price_100" onclick="secondTracker._trac…

    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 1166, Column 156: entity was defined here
    …e=Merchandising&utm_campaign=Banner_HP&utm_medium=Price_50" onclick="secondTra…
  • Error Line 1167, Column 393: required attribute "ALT" not specified
    …0euro.png" width="150" height="100" border="0" style="display:block;"></a></td>

    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 1174, Column 143: required attribute "ALT" not specified
    …r/bordo_left.png" width="1" height="99" border="0" style="display:block;"></td>

    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 1182, Column 176: reference to entity "departureAirports" for which no system identifier could be generated
    …chstatic.action?sl=1&departureAirports=AFRA&arrivalAirports=BCN&maxPrice=50&fr…

    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 1166, Column 73: entity was defined here
    …y.fr/vg1/pricesearchstatic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_…
  • Warning Line 1182, Column 182: cannot generate system identifier for general entity "arrivalAirports"
    …ic.action?sl=1&departureAirports=AFRA&arrivalAirports=BCN&maxPrice=50&fromDate…

    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 1182, Column 182: general entity "arrivalAirports" not defined and no default entity
    …ic.action?sl=1&departureAirports=AFRA&arrivalAirports=BCN&maxPrice=50&fromDate…

    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.

  • Error Line 1182, Column 197: reference to entity "arrivalAirports" for which no system identifier could be generated
    …departureAirports=AFRA&arrivalAirports=BCN&maxPrice=50&fromDate=2010-04-01&toD…

    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 1182, Column 181: entity was defined here
    …tic.action?sl=1&departureAirports=AFRA&arrivalAirports=BCN&maxPrice=50&fromDat…
  • Error Line 1182, Column 210: reference to entity "maxPrice" for which no system identifier could be generated
    …orts=AFRA&arrivalAirports=BCN&maxPrice=50&fromDate=2010-04-01&toDate=2010-07-3…

    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 1166, Column 96: entity was defined here
    …tic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&ut…
  • Warning Line 1182, Column 214: cannot generate system identifier for general entity "fromDate"
    …=AFRA&arrivalAirports=BCN&maxPrice=50&fromDate=2010-04-01&toDate=2010-07-30&ut…

    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 1182, Column 214: general entity "fromDate" not defined and no default entity
    …=AFRA&arrivalAirports=BCN&maxPrice=50&fromDate=2010-04-01&toDate=2010-07-30&ut…

    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.

  • Error Line 1182, Column 222: reference to entity "fromDate" for which no system identifier could be generated
    …rivalAirports=BCN&maxPrice=50&fromDate=2010-04-01&toDate=2010-07-30&utm_source…

    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 1182, Column 213: entity was defined here
    …s=AFRA&arrivalAirports=BCN&maxPrice=50&fromDate=2010-04-01&toDate=2010-07-30&u…
  • Warning Line 1182, Column 234: cannot generate system identifier for general entity "toDate"
    …s=BCN&maxPrice=50&fromDate=2010-04-01&toDate=2010-07-30&utm_source=Merchandisi…

    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 1182, Column 234: general entity "toDate" not defined and no default entity
    …s=BCN&maxPrice=50&fromDate=2010-04-01&toDate=2010-07-30&utm_source=Merchandisi…

    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.

  • Error Line 1182, Column 240: reference to entity "toDate" for which no system identifier could be generated
    …maxPrice=50&fromDate=2010-04-01&toDate=2010-07-30&utm_source=Merchandising&utm…

    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 1182, Column 233: entity was defined here
    …ts=BCN&maxPrice=50&fromDate=2010-04-01&toDate=2010-07-30&utm_source=Merchandis…
  • Error Line 1182, Column 262: reference to entity "utm_source" for which no system identifier could be generated
    …010-04-01&toDate=2010-07-30&utm_source=Merchandising&utm_campaign=Banner_HP&ut…

    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 1166, Column 108: entity was defined here
    …l=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&utm_campaign=B…
  • Error Line 1182, Column 289: reference to entity "utm_campaign" for which no system identifier could be generated
    …&utm_source=Merchandising&utm_campaign=Banner_HP&utm_medium=barcelona_BCN"><im…

    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 1166, Column 133: entity was defined here
    …A&maxPrice=50&utm_source=Merchandising&utm_campaign=Banner_HP&utm_medium=Price…
  • Error Line 1182, Column 310: reference to entity "utm_medium" for which no system identifier could be generated
    …sing&utm_campaign=Banner_HP&utm_medium=barcelona_BCN"><img src="http://www1.st…

    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 1166, Column 156: entity was defined here
    …e=Merchandising&utm_campaign=Banner_HP&utm_medium=Price_50" onclick="secondTra…
  • Error Line 1182, Column 452: required attribute "ALT" not specified
    …cellona.png" width="69" height="99" border="0" style="display:block;"></a></td>

    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 1183, Column 131: required attribute "ALT" not specified
    …mmon/space1x1.gif" width="4" height="5" border="0" style="display:block;"></td>

    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 1192, Column 173: reference to entity "departureAirports" for which no system identifier could be generated
    …chstatic.action?sl=1&departureAirports=AFRA&arrivalAirports=VCE&maxPrice=100&u…

    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 1166, Column 73: entity was defined here
    …y.fr/vg1/pricesearchstatic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_…
  • Error Line 1192, Column 194: reference to entity "arrivalAirports" for which no system identifier could be generated
    …departureAirports=AFRA&arrivalAirports=VCE&maxPrice=100&utm_source=Merchandisi…

    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 1182, Column 181: entity was defined here
    …tic.action?sl=1&departureAirports=AFRA&arrivalAirports=BCN&maxPrice=50&fromDat…
  • Error Line 1192, Column 207: reference to entity "maxPrice" for which no system identifier could be generated
    …orts=AFRA&arrivalAirports=VCE&maxPrice=100&utm_source=Merchandising&utm_campai…

    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 1166, Column 96: entity was defined here
    …tic.action?sl=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&ut…
  • Error Line 1192, Column 222: reference to entity "utm_source" for which no system identifier could be generated
    …alAirports=VCE&maxPrice=100&utm_source=Merchandising&utm_campaign=Banner_HP&ut…

    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 1166, Column 108: entity was defined here
    …l=1&departureAirports=AFRA&maxPrice=50&utm_source=Merchandising&utm_campaign=B…
  • Error Line 1192, Column 249: reference to entity "utm_campaign" for which no system identifier could be generated
    …&utm_source=Merchandising&utm_campaign=Banner_HP&utm_medium=venice_VCE" ><img …

    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 1166, Column 133: entity was defined here
    …A&maxPrice=50&utm_source=Merchandising&utm_campaign=Banner_HP&utm_medium=Price…
  • Error Line 1192, Column 270: reference to entity "utm_medium" for which no system identifier could be generated
    …sing&utm_campaign=Banner_HP&utm_medium=venice_VCE" ><img src="http://www1.stat…

    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 1166, Column 156: entity was defined here
    …e=Merchandising&utm_campaign=Banner_HP&utm_medium=Price_50" onclick="secondTra…
  • Error Line 1192, Column 407: required attribute "ALT" not specified
    …venezia.png" width="69" height="99" border="0" style="display:block;"></a></td>

    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 1193, Column 143: required attribute "ALT" not specified
    …r/bordo_left.png" width="1" height="99" border="0" style="display:block;"></td>

    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 1198, Column 135: required attribute "ALT" not specified
    …ordo_bottom.png" width="300" height="1" border="0" style="display:block;"></td>

    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 1471, Column 287: NET-enabling start-tag requires SHORTTAG YES
    …www3.staticroot.com/images/feedback/flights-fr.gif" style="border:none;" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1471, Column 287: required attribute "ALT" not specified
    …www3.staticroot.com/images/feedback/flights-fr.gif" style="border:none;" /></a>

    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 1508, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …9430768/?label=-8RECPbymwIQ8OjR7wM&amp;guid=ON&amp;script=0"/></div></noscript>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1512, Column 57: required attribute "TYPE" not specified
            <script src="http://nxtck.com/act.php?zid=33038"></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>.

  • Error Line 1517, Column 57: required attribute "TYPE" not specified
            <script src="http://nxtck.com/act.php?zid=35532"></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>.

  • Error Line 1541, Column 10: 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 1875, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …main-footer/credit-cards/footer_loghi_carte_fr.gif" alt="Credit Cards" /></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1878, Column 144: NET-enabling start-tag requires SHORTTAG YES
    …ofly SA. Copyright &copy; 2006-2013 Bravofly.com - Tous droits réservés. <br />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Visitor Analysis

Daily Visitor
  • 5.950 visits
Daily Visitor