Failure to display keys with a colon in the name

[luispollo]

When a key has a ':' in its name, the browser is cancelling the request, apparently due to a mal-formed location header in the redirect response from the server:

$ curl -I http://myhost/etcd/test/does_work
HTTP/1.1 302 Found
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Date: Mon, 19 Sep 2016 15:18:48 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store
Location: http://myhost/etcd/test/does_work;jsessionid=19komblrx0muvjix1tgzp3cc6?0
(...)

$ curl -I http://myhost/etcd/test/doesnt:work
HTTP/1.1 302 Found
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Date: Mon, 19 Sep 2016 15:18:53 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store
Location: doesnt:work;jsessionid=a41uqdoyk8ldu6c90ikwhs85?0

[luispollo]

@nikfoundas I spent quite some time trying to debug this so I could contribute a fix, but unfortunately I'm not familiar with Wicket and so I'm stuck. Do you have any idea what could be causing this? I was unable to find why Wicket returns a 302 (redirect) in the first place, and in any case can't spot anything in the logs that would indicate errors anywhere. Please help.