Shouldn't you look for https: as well as a possible likely request? I've seen several occurances where a special domain is setup for secure stuff - e.g. www.mydomain.com -> shop.mydomain.com which switches to https: in the process.
Also, ftp:// would defeinitely need to be in there. chanoch ------------------------------------------------------------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Although we routinely screen for viruses, recipients should check this e-mail and any attachment for viruses. We make no warranty as to absence of viruses in this e-mail or any attachments. -----Original Message----- From: Eddie Bush [mailto:ekbush@;swbell.net] Sent: 18 October 2002 16:37 To: Struts Developers List Subject: Re: Going to other context and/or server in 1.1 David Graham wrote: > I thought of the http:// matching as well. Are there any cases when > this logic wouldn't work? Hardcoding the protocol may be a bad idea. I don't like that idea either, but I can't think of a better approach. As I said, I'm open to suggestions :-) You could look for /word.word.word/, but I think that would be ... just as bad and a lot nastier to implement. Very problematic, I would think. Looking for "http:" seems the best solution that I can think of. > David -- Eddie Bush -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
