W3C home > Mailing lists > Public > www-validator-css@w3.org > July 2001

Valiator error occurs when validating css file first parsed server-side - any ideas?

From: Michael S. Bradley, Jr. <mike.bradley.jr@projexsys.com>
Date: Thu, 5 Jul 2001 08:24:59 -0400
Message-ID: <002401c1054d$82ad4a20$9765a8c0@snet.unrealsystems.com>
To: <www-validator-css@w3.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I truly appreciate any advice or insight you might offer and
understand that your time is surely limited in that regard. I would
have posted this question to the appropriate w3c list, but the one
associated with the css validator appears to be filled with spam, but
that may be a misunderstanding on my part.

My first attempt at proper XHTML and stylesheet implementation ...

    http://www.unrealsystems.com/

The stylesheet for the root directory's default (and only) document
is linked and you can view it directly in a browser ...

    http://www.unrealsystems.com/css/unrealsystems.css

Now, if you submit the same URI to the validator the following error
is returned:

"Target: http://www.unrealsystems.com/css/unrealsystems.css
I/O Error: Can't process the object
http://www.unrealsystems.com/css/unrealsystems.css "

When you view the style sheet directly in the browser or "see it
implemented" on the default document, your browser is actually
receiving content that has been parsed by a ColdFusion application
server ( http://www.allaire.com ). If I tell the application server
NOT to parse ".css" files then the error is not encountered. By the
way, having the application server parse the file beforehand is nice
because it means I can perform extensive customization to various
portions of my web site via a single style sheet that is generated on
the fly as opposed to using multiple style sheets that are linked
according to what portion of the site is being viewed.

For the life of me I don't know why the validator would care or even
know it was dealing with a dynamically generated file, my only guess
being that the validator does not like CGI interfaces.

Can you shed any light on this?

I realize there are other possible ways to use the validator, but in
the future when I'm applying CSS and XHTML throughout my other (much
much more extensive) websites, direct validation through URIs would
be a major advantage considering the stylesheets in question will be
dynamically generated.

Thanks for your help and the invaluable services the W3C provides to
the world at large.


Best regards,

Mike Bradley, Jr.
CTO and Co-founder
projeXsys, Inc.

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBO0RcmEbp+ZefHGx3EQJm0gCgt8rWcAxAeefTqTs7P9KEVPA0LLcAn0BV
5DoGLnKnFBzlCUKH9v7O8fE/
=ppnV
-----END PGP SIGNATURE-----
Received on Thursday, 5 July 2001 08:30:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 June 2012 00:13:59 GMT