Friday, March 29, 2002

An interesting experiment: I added win32 status to my server logs a while ago and made a reminder to check the results: it popped up this morning. I did a grep -e"- 5[0-9][0-9] [1-9]" * to find all the 500 range errors with non-zero win32 error codes. Sadly, nothing. (The 500 errors are the ones that could most benefit from some help from Win32). Same with the 300 range. The 200 range had 2 win32 errors with 200 HTTP responses: 64 and 22. The always useful Net HelpMSG nn told me that 64 is The specified network name is no longer available and 22 is The device does not recognize the command. I don't see how a 200 HTTP code can match either of these. In the 400 series, I found these combinations: 401 5, 403 5, 404 2, 404 3, 405 1. 401 is Unauthorized and 403 is Forbidden, so the win32 5 ("Access is denied") doesn't add a whole lot. 404 is, of course, Not found, so the win32 codes divide that into 2 (The system cannot find the file specified) and 3 (The system cannot find the path specified), distinguishing between directory name errors and file name errors. 405 is Method not allowed and win32 1 is Incorrect function. Those errors were on a FrontPage module, author.dll, so I don't know what's going on there. FrontPage Extensions is only installed because ASP.NET put it there; I dislike the directory clutter. A fun hour, but I'd better get back to work. 8:54:29 AM

© Copyright 2002 John Sands.