Hi,
we became aware of a problem caused by requests with invalid URIs on
our wicket-application. The URI contains strings like *://*:*, so
wicket tries to determine and parse a port number, that is not
present. This leads to NumberFormatExceptions with URIs like, e.g.
http://host/h@@p://h@@p://
(wicket.apache.org, url.getHost());
assertEquals(/h@@p://h@@p://, url.getPath());
}
Works fine with 6.10.0-SNAPSHOT.
Sven
On 07/24/2013 10:29 AM, Mathias Binder wrote:
Hi,
we became aware of a problem caused by requests with invalid URIs on
our wicket-application. The URI contains
