URL validation

[David Bowers <vi...@gmail.com>]

There was a very good conversation in April on this list discussing
URL validation, in particular, is an http URL valid if no path is
specified?  For example http://google.com.

See this link: http://www.mail-archive.com/dev@struts.apache.org/msg00037.html
for more detail.

It seemed like the consensus was that it would be good if this
behavior could be turned on or off.  What is the current status of
this?  It looks like a patch was submitted related to this issue: 
http://issues.apache.org/bugzilla/show_bug.cgi?id=28190, though it's
not obvious that this would solve the problem.  This patch would tell
us exactly why http://google.com failed, but it does not seem to
provide the flexibility to just allow http://google.com to succeed.

Is there an interest in modifying the url validator to take an
variable called lenientPath?  That way if the path ends with a / or is
null it would still pass?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: URL validation

[Niall Pemberton <ni...@blueyonder.co.uk>]

Url validation is part of Commons Validator rather than Struts so it might
be more appropriate to raise it there.

Also, this is subject to an outstanding bug:

http://issues.apache.org/bugzilla/show_bug.cgi?id=30686

Niall

----- Original Message ----- 
From: "David Bowers" <vi...@gmail.com>
To: <de...@struts.apache.org>
Sent: Friday, November 12, 2004 6:49 PM
Subject: URL validation


> There was a very good conversation in April on this list discussing
> URL validation, in particular, is an http URL valid if no path is
> specified?  For example http://google.com.
>
> See this link:
http://www.mail-archive.com/dev@struts.apache.org/msg00037.html
> for more detail.
>
> It seemed like the consensus was that it would be good if this
> behavior could be turned on or off.  What is the current status of
> this?  It looks like a patch was submitted related to this issue:
> http://issues.apache.org/bugzilla/show_bug.cgi?id=28190, though it's
> not obvious that this would solve the problem.  This patch would tell
> us exactly why http://google.com failed, but it does not seem to
> provide the flexibility to just allow http://google.com to succeed.
>
> Is there an interest in modifying the url validator to take an
> variable called lenientPath?  That way if the path ends with a / or is
> null it would still pass?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org