done
https://issues.apache.org/jira/browse/WICKET-5287
2013/7/25 Sven Meier
> ServletWebRequest#**getContextRelativeUrl() passes "foo://:/" to
> Url#parse() and that one fails.
>
> Please create a Jira issue.
>
> Sven
>
>
> On 07/24/2013 05:06 PM, Martin Funk wrote:
>
>> Hi Sven,
>>
>> we still
ServletWebRequest#getContextRelativeUrl() passes "foo://:/" to
Url#parse() and that one fails.
Please create a Jira issue.
Sven
On 07/24/2013 05:06 PM, Martin Funk wrote:
Hi Sven,
we still can reproduce this on any version.
Maybe this git diff gives a clearer picture:
diff --git
a/wicket-c
Hi Sven,
we still can reproduce this on any version.
Maybe this git diff gives a clearer picture:
diff --git
a/wicket-core/src/test/java/org/apache/wicket/protocol/http/servlet/ServletWebRequestTest.java
b/wicket-core/src/test/java/org/apache/wicket/protocol/http/servlet/ServletWebRequestTest.ja
We work with Version 6.7.0
Mathias
2013/7/24 Sven Meier :
> Hi,
>
> which Wicket version? Url parsing has been improved on lately:
>
> @Test
> public void weirdUrl()
> {
> Url url = Url.parse("http://wicket.apache.org/h@@p://h@@p://";);
>
> assertEquals("wicket.apache.
Hi,
which Wicket version? Url parsing has been improved on lately:
@Test
public void weirdUrl()
{
Url url = Url.parse("http://wicket.apache.org/h@@p://h@@p://";);
assertEquals("wicket.apache.org", url.getHost());
assertEquals("/h@@p://h@@p://", url.getPath())
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:///h@@p://h@@p://
jav
