Bluecoat weirdness

One of the things that I spent a good portion of a day on last week was the installation of a new BlueCoat SG800-0B. This is a web-caching appliance to replace our rapidly aging W2K/ISA2K box. BlueCoat used to be known as Cacheflow and is basically the only surviving web caching appliance maker. There were two main reasons I got this particular product. First, was to get a better performing and easier to manage (eventually) web caching solution. Second, was to be able to have a transparent proxy that can do authentication and tracking. The transparency was important as it would allow our teachers and students to longer have to worry about enabling and disabling the proxy server on their laptops when they left our network. In researching this product I read the document available here about configuring the appliance for transparency. Everything looked good. I also spoke to BlueCoat sales and tech people about my planned install. Lastly, I had a consultant from the reseller we purchased from True North Solutions come out and install the box. Later in the week I was testing the box before I switched over to it in production. It was at this point that I realized the box was not properly passing HTTPS traffic. I called BlueCoat and was informed that this was normal in transparent mode, apparently the box can't handle HTTPS in that configuration. Additionally I was informed that I was mostly running in an unsupported configuration. As I had gone through the process of purchasing and installing this device the problem of HTTPS was never brought to my attention. At this point I have the box in production and I will continue to investigate the HTTPS problem. I am just a little annoyed that none of the people I talked to brought this up as a problem. It also reinforces that I should be installing most of this stuff myself and learning what I need to do it. I was hoping for once I could rely on outside help.