headers
Dejan Tolj | 1 Jun 2009 01:46
Picon

unable to start Apache

I installed the w3c markup validator and configured Apache webserver
using this guide:
http://validator.w3.org/docs/install.html#install-package
However when I start the webserver it complains about:

Starting httpd: Syntax error on line 20 of /etc/w3c/validator.conf:
Invalid command '<Paths', perhaps misspelled or defined by a module
not included in the server configuration

Am I missing some 3rd party apache module?
Please advise.
Thanks.
Permalink | Reply | 2 comments |
headers
Ville Skyttä | 1 Jun 2009 19:35
Picon
Picon
Favicon

Re: unable to start Apache

On Monday 01 June 2009, Dejan Tolj wrote:
> I installed the w3c markup validator and configured Apache webserver
> using this guide:
> http://validator.w3.org/docs/install.html#install-package
> However when I start the webserver it complains about:
>
> Starting httpd: Syntax error on line 20 of /etc/w3c/validator.conf:
> Invalid command '<Paths', perhaps misspelled or defined by a module
> not included in the server configuration

I guess your Apache some way ends up reading /etc/w3c/validator.conf.  This is 
not going to work; that file should be read by validator's "check" script 
only.  Make sure your Apache configuration files do not have an "Include" 
directive pointing to that file/dir.
Permalink | Reply | 1 comment |
headers
Matt Salmon | 2 Jun 2009 10:22

Question regarding W3C validator and ASP.NET

Can anyone help me with a query regarding validation of asp.net pages. I’ve searched these mailing lists but nobody seems to have answered this exact question.

 

Basically, ASP.NET 2.0 can enhance the way pages are rendered in order to conform with xhtml 1.0 strict, using a configuration setting. This has the effect of removing the ‘name’ attribute from the form element, wrapping the hidden asp.net fields in a ‘div’ element and some other changes.

 

The issue with the hidden fields is that the ID’s start with an underscore character e.g “__VIEWSTATE”, however what I can’t understand is how wrapping the fields in an outer ‘div’ results in a ‘pass’ from the validation service? Surely the ID’s still start with an underscore character regardless of the fact they’re in a containing element?

 

Can anyone shed any light on this?

 

Matt Salmon
Head of Programming

Liverpool Science Park
131 Mount Pleasant
Liverpool L3 5TF

t: +44 (0) 845 365 4040
f: +44 (0) 845 365 4041
w: www.mandogroup.com

Mando Group Ltd
Registered in England 04391789

The contents of this email are strictly private and confidential and are intended solely for the named addressee[s] only. If you are not the intended recipient, you should not copy it or use it for any purpose, nor disclose its contents to any other person and you should return this message to the sender and delete it from your mailbox. The views and opinions expressed in this email do not necessarily represent those of Mando Group. Please note that whilst Mando Group does check for viruses, it is the responsibility of the recipient to scan all messages prior to opening them.

 

Permalink | Reply | 1 comment |
headers
David Dorward | 2 Jun 2009 10:55
Picon
Favicon
Gravatar

Re: Question regarding W3C validator and ASP.NET

<quote who="Matt Salmon">

> Basically, ASP.NET 2.0 can enhance the way pages are rendered in order
> to conform with xhtml 1.0 strict, using a configuration setting. This
> has the effect of removing the 'name' attribute from the form element,
> wrapping the hidden asp.net fields in a 'div' element and some other
> changes.

Only Microsoft would describe a bug fix as an "enhancement".

> The issue with the hidden fields is that the ID's start with an
> underscore character e.g "__VIEWSTATE",

Correct

> however what I can't understand
> is how wrapping the fields in an outer 'div' results in a 'pass' from
> the validation service?

The child element of a form must be an element in the group %block (other
than form). Inputs are not in that group, div elements are. Div elements
are allowed to contain inputs.

Starting an id with an underscore is a seperate issue. The setting may or
may not fix that.

Note that a control _name_ MAY start with an underscore, and there is
usually no reason to give a hidden input an id, so it is possible you are
just confusing names and ids here.

Seeing the difference in the code outputted in the two modes might help us
shed more light on the matter.

(Please direct responses to the www-validator mailing list and not
directly to me).

--

-- 
David Dorward
http://dorward.me.uk/
Permalink | Reply | 0 comments |
headers
Matt Salmon | 2 Jun 2009 11:19

Re: Question regarding W3C validator and ASP.NET

Ok, here’s some example output given the 3 possible xhtml conformance modes offered by asp.net

 

<xhtmlConformance mode="Legacy"/>

<body>

    <form name="form1" method="post" action="default.aspx" id="form1">

<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUJNzgzNDMwNTMzZGSXoVqQ0i3LT5svrbSOWojE+R7IzA==" />

 

    <div>

   

    </div>

    </form>

</body>

 

<xhtmlConformance mode="Transitional"/>

<body>

    <form name="form1" method="post" action="default.aspx" id="form1">

<div>

<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUJNzgzNDMwNTMzZGSXoVqQ0i3LT5svrbSOWojE+R7IzA==" />

</div>

 

    <div>

   

    </div>

    </form>

</body>

 

<xhtmlConformance mode="Strict"/>

<body>

    <form method="post" action="default.aspx" id="form1">

<div>

<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUJNzgzNDMwNTMzZGSXoVqQ0i3LT5svrbSOWojE+R7IzA==" />

</div>

 

    <div>

   

    </div>

    </form>

</body>

 

You’ll notice that in both transitional and strict modes, the viewstate field gets wrapped in a div. Running each of these through the w3c validator shows that this does in fact solve the validation error regarding the underscore character in the id attribute, but if the rule says ‘id’s can’t start with an underscore I don’t understand how the extra div helps; the input id still starts with an underscore!

Matt Salmon
Head of Programming

Liverpool Science Park
131 Mount Pleasant
Liverpool L3 5TF

t: +44 (0) 845 365 4040
f: +44 (0) 845 365 4041
w: www.mandogroup.com

Mando Group Ltd
Registered in England 04391789

The contents of this email are strictly private and confidential and are intended solely for the named addressee[s] only. If you are not the intended recipient, you should not copy it or use it for any purpose, nor disclose its contents to any other person and you should return this message to the sender and delete it from your mailbox. The views and opinions expressed in this email do not necessarily represent those of Mando Group. Please note that whilst Mando Group does check for viruses, it is the responsibility of the recipient to scan all messages prior to opening them.

 

Permalink | Reply | 2 comments |
headers
David Dorward | 2 Jun 2009 11:38
Picon
Favicon
Gravatar

Re: Question regarding W3C validator and ASP.NET

<quote who="Matt Salmon">
> Ok, here's some example output given the 3 possible xhtml conformance
> modes offered by asp.net

Since they all have an invalid xhtmlConformance element and since none
have a Doctype - none of those are valid.

Perhaps what ASP.NET outputs when given those documents as input is, but
that isn't what you are showing us.

--

-- 
David Dorward
http://dorward.me.uk/
Permalink | Reply | 0 comments |
headers
Michael A. Peters | 2 Jun 2009 11:38
Picon

Re: Question regarding W3C validator and ASP.NET

Matt Salmon wrote:

>  
> 
> You’ll notice that in both transitional and strict modes, the viewstate 
> field gets wrapped in a div. Running each of these through the w3c 
> validator shows that this does in fact solve the validation error 
> regarding the underscore character in the id attribute, but if the rule 
> says ‘id’s can’t start with an underscore I don’t understand how the 
> extra div helps; the input id /still/ starts with an underscore!

I'm not sure about the underscore thing but an input node can not be a 
direct child of a form node.

An input can be child of fieldset, div, maybe some others, but not form.
Why the spec was written that way I don't know, but that's the way it is.
Permalink | Reply | 0 comments |
headers
Matt Salmon | 2 Jun 2009 13:59

Re: Question regarding W3C validator and ASP.NET

I never stated that what I posted was valid, I was merely trying to illustrate the differences in the rendered markup that the same .aspx template can generate given 3 possible configuration settings.  Let me put it another way; the asp.net XML configuration file can have 3 possible settings

<xhtmlConformance mode="Legacy"/>

<xhtmlConformance mode="Transitional"/>

<xhtmlConformance mode="Strict"/>

 

The rendered markup for each of these settings, respectively (with ‘input’ errors now corrected), is:

 

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >

<head><meta http-equiv="Content-type" content="text/html;charset=UTF-8"><title>

        Untitled Page

</title></head>

<body>

    <form name="form1" method="post" action="default.aspx" id="form1">

<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUJMTQ5ODEyODUyZGQ=" />

 

<input type="hidden" name="__EVENTVALIDATION" id="__EVENTVALIDATION" value="/wEWAwL7z8SCCAKsyrLrBgKs34rGBg==" />

    <p><input name="textbox1" type="text" id="textbox1" /></p>

    <p><input type="submit" name="button1" value="" id="button1" /></p>

    </form>

</body>

</html>

 

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >

<head><meta http-equiv="Content-type" content="text/html;charset=UTF-8" /><title>

        Untitled Page

</title></head>

<body>

    <form name="form1" method="post" action="default.aspx" id="form1">

<div>

<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUJMTQ5ODEyODUyZGQ=" />

</div>

 

<div>

 

        <input type="hidden" name="__EVENTVALIDATION" id="__EVENTVALIDATION" value="/wEWAwL7z8SCCAKsyrLrBgKs34rGBg==" />

</div>

    <p><input name="textbox1" type="text" id="textbox1" /></p>

    <p><input type="submit" name="button1" value="" id="button1" /></p>

    </form>

</body>

</html>

 

 

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >

<head><meta http-equiv="Content-type" content="text/html;charset=UTF-8" /><title>

        Untitled Page

</title></head>

<body>

    <form method="post" action="default.aspx" id="form1">

<div>

<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUJMTQ5ODEyODUyZGQ=" />

</div>

 

<div>

 

        <input type="hidden" name="__EVENTVALIDATION" id="__EVENTVALIDATION" value="/wEWAwL7z8SCCAKsyrLrBgKs34rGBg==" />

</div>

    <p><input name="textbox1" type="text" id="textbox1" /></p>

    <p><input type="submit" name="button1" value="" id="button1" /></p>

    </form>

</body>

</html>

 

So then, leaving aside semantics and pedantics, is anyone actually able to answer my question… why does wrapping the input in a div mean that the W3C validator ignores the id underscore rule?

 

 

Matt Salmon
Head of Programming

Liverpool Science Park
131 Mount Pleasant
Liverpool L3 5TF

t: +44 (0) 845 365 4040
f: +44 (0) 845 365 4041
w: www.mandogroup.com

Mando Group Ltd
Registered in England 04391789

The contents of this email are strictly private and confidential and are intended solely for the named addressee[s] only. If you are not the intended recipient, you should not copy it or use it for any purpose, nor disclose its contents to any other person and you should return this message to the sender and delete it from your mailbox. The views and opinions expressed in this email do not necessarily represent those of Mando Group. Please note that whilst Mando Group does check for viruses, it is the responsibility of the recipient to scan all messages prior to opening them.

 

Permalink | Reply | 501 comments |
headers
David Dorward | 2 Jun 2009 15:16
Picon
Favicon
Gravatar

Re: Question regarding W3C validator and ASP.NET

<quote who="Matt Salmon">

> So then, leaving aside semantics and pedantics, is anyone actually able
> to answer my question... why does wrapping the input in a div mean that
> the W3C validator ignores the id underscore rule?

It doesn't.

... but some more testing showed that that error isn't reported for any of
those three documents in the first place.

Some more poking shows that while the HTML 4.01 DTDs define the id
attribute as containing a NAME token. the XHTML 1.0 DTDs define it as
having an XML ID token, which can start with an underscore.

This is mentioned in the spec <http://www.w3.org/TR/xhtml1/#h-4.10> and in
Appendix C <http://www.w3.org/TR/xhtml1/#C_8> and in the XHTML media types
document <http://www.w3.org/TR/xhtml-media-types/#C_8>

--

-- 
David Dorward
http://dorward.me.uk/
Permalink | Reply | 501 comments |
headers
Shivanand | 2 Jun 2009 16:21
Picon

checklink:

Hello,

                                 I configured Link checker in my local machine when I am trying to test URL its giving me an error is as follow

” Error: 403 Checking non-public IP address disallowed by link checker configuration+apche web server”. Please guide me to resolve this error.

 

Thanks and Regards

Shivanand



--
Thanks & Regards,
Shivanand
Permalink | Reply | 4 comments |

Gmane