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>

Reply via email to