- From: Terje Bless <link@tss.no>
- Date: Wed, 8 Sep 1999 22:19:34 +0200
- To: W3C Validator <www-validator@w3.org>
- Message-Id: <199909082013.WAA04292@vals.intramed.rito.no>
('binary' encoding is not supported, stored as-is)
Here is the patch (against 1.31) to make "check" use CGI.pm. It does away with the ability to put parameters in path info, but includes a special case to allow you continue to use "/check/referer" to check the referer. It's been reasonably well tested, so I don't anticipate any problems, but as it's a fairly comprehenive change something may have snuck in. If any problems pop up I'll try to fix them ASAP. If this works well I'll start work on silencing the warnings from -w (how's your error logs looking Gerald? ;D), followed by some general code cleanup, followed by making the output valid. If anyone has any requests -- from the official TODO list! -- that they want me to prioritize, let me know and I'll see how it fits with my own plans. If anyone have requests that _aren't_ on the official TODO list, the mailinglist or Gerald is probably the place to ask. Feel free to CC me, of course, but I'm giving priority to the TODO list; and since I'm not in any way involved with the validator, the real maintainer (that would be Gerald ;D) won't know about it if you just send it to me. BTW, Gerald, you might want to disable -w in the running copy of the validator if you haven't allready. 1.31 produces up to 1500 lines of (mostly harmless) warnings per run (under some circumstances (mainly the parse tree code)); all of which end up in the error_log. I'll try to provide a patch to clean this up once I manage to make some sense out of the code in question. -link -- *** I just switched to a new email client. *** If you see any format problems in this message, yell. Loudly! :-) -link
Attachments
- application/octet-stream attachment: CGIpm.diff
Received on Wednesday, 8 September 1999 16:14:13 UTC