>> Can you try it again with current cvs HEAD? I'm not familiar with the >> W3C >> Validator test, but I would hope that if it saw a good http Content-Type >> header, >> it wouldn't need the stuff in the html meta line. > > Me too but I found a problem/feature due to the validator so I just wrote > the > following email to the w3c validator team:
Just turn off the validator feature for detecting charset through the META tag. That check is bogus anyway and the W3C knows it. The charset of the error documents is iso-8859-1, which is the default for HTTP. Someone could try adding the meta tag to the HTML output instead of on the content-type, but then they would have to check to see if this still reduces the cross-site scripting problems that Marc found earlier. ....Roy
