You are accessing the archives. Commenting has been disabled, and archive posts are likely to be horribly out of date and, in some cases, rendered oddly because the styles from archive posts are no longer being maintained.
May 10, 2007

Microsoft's Failure to Stand

I've been using Linux as my primary operating system since 1999. I've also done my best to have a Windows system around as well, regardless of how underpowered the machine running it is. I cut my teeth in IT at a Windows only shop, and managed to become MCP certified, with the intention of getting an MCSE. *yawn* However, then I got my current development job and all the grand plans for certification we out the door (because I only wanted them to get a better job).

The nature of web development, however, means you need to be familiar with many different browsing environments, OS and browser-wise. So yes, I've got a Windows box, and a Windows VM, and a few Windows laptops at work that I use on a regular basis to get full coverage on our development progress.

A Failure to Communicate

We've decided to evaluate the use of WebDAV in our development environment at work. I've done this a few times before, so I'm familiar with how to implement it on the apache side. So I set everything up, and then installed a commandline dav client called cadaver on my machine. It worked like a charm. So then I went over to my Windows box and tried connecting with "Web Folders." However, no matter how hard I tried, the authentication wouldn't work. I tried switching Apache to AuthBasic from AuthDigest and back, to no avail. While looking for another client I could test with, I stumbled across this article, detailing Microsoft's poor DAV client integration. I was finally able to authenticate by adding a "#" at the end of the url to connect to. Intuitive huh?

No comments have been posted yet.
Comments are now closed an archived posts.