On Thu, 13 Aug 1998, Cybertech wrote:
> search engines and of cource now it can't be found because of the http://.
> And finally, if you type in the actual address for the site, ie:
> http://www.myserver.com/~site, then it is not secure. Any way around this
> too?
Salve,
rewriting works, I'm doing it w/ a few million request a week, have a
try at http://www.ccc.de . There are disadvantages, as there are quite a
few not beeing able to https to your Site. It's up to you if you want to
exclude them. Biggest Trouble makers in sorted order:
1. IE [3|4].*: own CA certs are downladed and saved to disk per default,
lot's of newbees doesn't know how to open directly. Sometimes the ssl
Connect is refused by the client, dunno why. PPC Macs are reported to
crash, when connecting to the site. When they don't crash they get an
error. Approx. 0.0 Mac-IE users have visited the Page. :(
2. Corporate Surfers are Firewall Lovers, quite a few of the things
don't allow 443, workaround: https://yoursite.com:80 (under construction
:)
3. Not working secure-proxies, eg Singapore and some stupid POP's. BTW,
I've never understood what a secure Proxy does. So maybe my fault.
Eris rUlEz :)
Pluto - SysAdmin of Hades
We are NSA, your mail will be scrutinzed, resistance is futile! =:-)
Key fingerprint: 1F 3F EA 94 D0 56 A6 86 4D 19 C4 56 6C F9 43 44
Stand on my shoulders, not on my toes.