Oops :-) can't you just take the path and encrypt that using the same strategy as the cryptedurl.. thingy is using?
Antoine On Mon, Mar 1, 2010 at 5:43 PM, Sergey Olefir <solf.li...@gmail.com> wrote: > > 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: > http://old.nabble.com/How-to-'resolve'-URL-in-stylesheet--td27720293.html > (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: > http://old.nabble.com/How-to-encrypt-obfuscate-resource-reference--tp27744679p27745911.html > 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 > > -- take your photos everywhere you go - https://www.memolio.com follow us on Twitter - http://twitter.com/Memolio --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
