- From: Karim A. <directeur@gmail.com>
- Date: Sat, 2 Feb 2008 14:18:55 +0100
- To: "David Dorward" <david@dorward.me.uk>
- Cc: "Nevena Jovanovic" <nevena.jovanovic@gmail.com>, "W3C Validator Community" <www-validator@w3.org>
David is right. If you use a template system in you app, I'd suggest to create static pages that "looks" like the ones behind the login area and check them. If these templates are valid, and the text/variables you inject in them are valid too, then the securised pages should be valid too. Karim -- http://xhtml-css.com Be Valid or die learning On Feb 2, 2008 8:51 AM, David Dorward <david@dorward.me.uk> wrote: > > > On 1 Feb 2008, at 22:52, Nevena Jovanovic wrote: > how can I check validation of my pages that are behind login area? > > > A couple of options are to: > > * Build a method into the the authentication / authorisation system that > allows access for the validator (this could be a username and password in > the query string, or something that works on the user agent and/or ip > address of the client - I suggest you install a local copy of the validator > on your network if you take this approach, otherwise you've built a very > public back door into your system). > > * Use the file upload feature of the validator to test your pages. The > Firefox Web Developer Toolbar has a "Validate Local HTML" option which makes > this a two click operation. > > -- > David Dorward > http://dorward.me.uk/ > http://blog.dorward.me.uk/ > >
Received on Saturday, 2 February 2008 13:19:05 UTC