Ovid Says > To be honest, while I don't know a simple answer for this, the reality is that this answer doesn't work very well. People can easily type stuff like:
http://blogs.server.somehost.co.uk/ http://foo.co.uk/ https://www.host.com/ Keith Says > Hmm... I agree with you. It's the same old programmers dilemma, do you go overboard and try to cater for every eventual possibility and trap every error or do you just build something quick that works and develop it later if you need to? Personally I always base that solution on the critical nature of project. Parking pages was my application... hmm... and I think no one will die if the junk traffic isn't captured and my directory and pop-ups aren't served to a few web surfers. But getting back on topic if you run those URIs through the script mentioned previously then you'd get... blogs.server.somehost.co.uk foo.co.uk Which I assume is what he's basically after, isn't it? and unless he's running an SSL server he'll never capture the https:// port anyhow. All I'm saying is, as a quick fix the 3 liner worked great and will probably suffice in most cases, if he gets problems he can always go in hack the script to work better. From experience, the majority of traffic is going be prefixed with http://www. or just http:// anyhow. Regards, Keith -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
