He he, that was my old thread there :)

Thing is, I just recently discovered, that encoding resources as arguments
(rather than paths) completely breaks relative URLs discussed there:
(for the simple reason that browser strips out arguments when resolving
relative url).

So it is necessary to come up with some other solution.

Antoine van Wel wrote:
> for a discussion and suggestion see
> http://old.nabble.com/CryptedUrlWebRequestCodingStrategy-%2B-WebRequestCodingStrategy-%3D-resource-URLs-are-not-encrypted-(bug-).-td27209560.html

View this message in context: 
Sent from the Wicket - User mailing list archive at Nabble.com.

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to