The good news: 

I've just persuaded a client to move away from Microsoft Proxy Servers to 
Apache for their reverse proxy requirements.

The not-quite-so-good news:

They still want to run it on Win2k, which is fair enough, since they have lots 
of Microsoft-experienced people around, are not going to get rid of supporting 
Windows, and the cost (INCLUDING SUPPORT) of 31 MS servers is LESS than the 
cost of 30 MS Servers plus 1 Linux server :-)

The oh-dear-what-have-I-got-myself-into news:

About 30 minutes AFTER I had set up Apache and demonstrated their requirement, 
a different team popped up and said "we need a reverse proxy as well - can this 
do it"? I said "Yes". They said, "How do we deal with HTTPS and Certificates"?

I said "I'll find out" :-)

Any ideas? Dummy URLS that give what I need???

M.