> You must be joking. We're charging them :) It's just the twisted way they
> like to deploy things.
"their own SSL accelerator" sounded like they had their own... my bad =)
> but of course that needs to be:
>
> https://whatever....
>
> if the accelarator is in use.
Wouldn't *any* web server behind this accelerator have a similar problem?
Where it wouldn't know that it's being SSL'd and thus return HTTP as the
scheme? Sounds to me like something the authors of this accelerator should
know about... actually deploying it =)
- r
