You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Korbinian Bachl <ko...@whiskyworld.de> on 2006/11/24 15:13:54 UTC
common URL encoding/ decoding (base64)
Hi,
some time ago i reportet http://issues.apache.org/jira/browse/WICKET-16
, wich was solved fast. However, the problem consits till today and so i
opened up http://issues.apache.org/jira/browse/WICKET-77
These was aimed at the missing decoding of these issues in pageparameters,
however, I now wonder if it wouldnt be better to give wicket a common URL
filter wich decodes and encodes all URLs before they are used/ released so
that these are solved forever.
Any comments on that?
Regards
AW: common URL encoding/ decoding (base64)
Posted by Korbinian Bachl <ko...@whiskyworld.de>.
yeah - thats my thought
i mean encoding is useless as long as we have no common decoding gateway,
right?
imagine, that you can build a wicket app where you can put additional info
into the url just before the app-root itself...
e.g:
site/mountpoint
site/additionalthings/mountpoint
without changing a single page, just the encode/ decode parts...
also we have to get rid of these UTF problems - i mean, if i do (pageParams)
params.add("1","hähä") i want go get "hähä" when calling getParam("1"); - no
the current mess :)
so, if we get rid of all at-the-place corrections of this, and finally
encode everything URL outgoing in base64/ utf 8/ any other strategy and
decode every URL incoming we are fine, arent we?
finally, using a way like this could enable users in certain cases to even
disable that behaviour or change the whole encoding from base64 to any other
possible encoding mechanism
do you see any dangers/ cons here?
regards
> -----Ursprüngliche Nachricht-----
> Von: Johan Compagner [mailto:jcompagner@gmail.com]
> Gesendet: Sonntag, 26. November 2006 16:09
> An: wicket-dev@incubator.apache.org
> Betreff: Re: common URL encoding/ decoding (base64)
>
> Reqeust.encodeUrl is the common base point where all urls are
> going through. But you also want a decode place where the
> incomming url (that can be any thing then, first passes through?)
>
> On 11/26/06, Korbinian Bachl <ko...@whiskyworld.de> wrote:
> > sounds very promising - like i wrote to eelco: if all URL
> things would
> > be centralised and go through 1 place at the end (encode)/ begining
> > (decode) then the world would be open to handle most
> special url needs easier - e.g:
> > language-tag in URLs, global needed params etc.
> >
> > as it could go this
> > /lang-tag/anybookmarkable-page
> > /lang-tag/?wicket=interface...
> >
> > so we could set up this without the need to limit ourself to 1
> > strategy all over the app...
> >
> > any comments from the core-programmers on this?
> >
> > Regards
> >
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Jean-Baptiste Quenot [mailto:jbq@apache.org]
> > > Gesendet: Sonntag, 26. November 2006 11:45
> > > An: wicket-dev@incubator.apache.org
> > > Betreff: Re: common URL encoding/ decoding (base64)
> > >
> > > * Korbinian Bachl:
> > >
> > > > These was aimed at the missing decoding of these
> issues in
> > > > pageparameters, however, I now wonder if it wouldnt be
> > > better to give
> > > > wicket a common URL filter wich decodes and encodes
> all URLs
> > > > before they are used/ released so that these are
> solved forever.
> > >
> > > Related to that: in « WICKET-65 Handle String array in
> > > PageParameters » I provide a generic WebRequestEncoder
> to factor
> > > out the URL-encoding instructions that stand all over the code.
> > > --
> > > Jean-Baptiste Quenot
> > > aka John Banana Qwerty
> > > http://caraldi.com/jbq/
> > >
> >
> >
>
Re: common URL encoding/ decoding (base64)
Posted by Johan Compagner <jc...@gmail.com>.
Reqeust.encodeUrl is the common base point where all urls are going
through. But you also want a decode place where the incomming url
(that can be any thing then, first passes through?)
On 11/26/06, Korbinian Bachl <ko...@whiskyworld.de> wrote:
> sounds very promising - like i wrote to eelco: if all URL things would be
> centralised and go through 1 place at the end (encode)/ begining (decode)
> then the world would be open to handle most special url needs easier - e.g:
> language-tag in URLs, global needed params etc.
>
> as it could go this
> /lang-tag/anybookmarkable-page
> /lang-tag/?wicket=interface...
>
> so we could set up this without the need to limit ourself to 1 strategy all
> over the app...
>
> any comments from the core-programmers on this?
>
> Regards
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Jean-Baptiste Quenot [mailto:jbq@apache.org]
> > Gesendet: Sonntag, 26. November 2006 11:45
> > An: wicket-dev@incubator.apache.org
> > Betreff: Re: common URL encoding/ decoding (base64)
> >
> > * Korbinian Bachl:
> >
> > > These was aimed at the missing decoding of these issues in
> > > pageparameters, however, I now wonder if it wouldnt be
> > better to give
> > > wicket a common URL filter wich decodes and encodes all URLs
> > > before they are used/ released so that these are solved forever.
> >
> > Related to that: in « WICKET-65 Handle String array in
> > PageParameters » I provide a generic WebRequestEncoder to
> > factor out the URL-encoding instructions that stand all over the code.
> > --
> > Jean-Baptiste Quenot
> > aka John Banana Qwerty
> > http://caraldi.com/jbq/
> >
>
>
AW: common URL encoding/ decoding (base64)
Posted by Korbinian Bachl <ko...@whiskyworld.de>.
sounds very promising - like i wrote to eelco: if all URL things would be
centralised and go through 1 place at the end (encode)/ begining (decode)
then the world would be open to handle most special url needs easier - e.g:
language-tag in URLs, global needed params etc.
as it could go this
/lang-tag/anybookmarkable-page
/lang-tag/?wicket=interface...
so we could set up this without the need to limit ourself to 1 strategy all
over the app...
any comments from the core-programmers on this?
Regards
> -----Ursprüngliche Nachricht-----
> Von: Jean-Baptiste Quenot [mailto:jbq@apache.org]
> Gesendet: Sonntag, 26. November 2006 11:45
> An: wicket-dev@incubator.apache.org
> Betreff: Re: common URL encoding/ decoding (base64)
>
> * Korbinian Bachl:
>
> > These was aimed at the missing decoding of these issues in
> > pageparameters, however, I now wonder if it wouldnt be
> better to give
> > wicket a common URL filter wich decodes and encodes all URLs
> > before they are used/ released so that these are solved forever.
>
> Related to that: in « WICKET-65 Handle String array in
> PageParameters » I provide a generic WebRequestEncoder to
> factor out the URL-encoding instructions that stand all over the code.
> --
> Jean-Baptiste Quenot
> aka John Banana Qwerty
> http://caraldi.com/jbq/
>
Re: common URL encoding/ decoding (base64)
Posted by Jean-Baptiste Quenot <jb...@apache.org>.
* Korbinian Bachl:
> These was aimed at the missing decoding of these issues in
> pageparameters, however, I now wonder if it wouldnt be better to
> give wicket a common URL filter wich decodes and encodes all
> URLs before they are used/ released so that these are solved
> forever.
Related to that: in « WICKET-65 Handle String array in
PageParameters » I provide a generic WebRequestEncoder to factor
out the URL-encoding instructions that stand all over the code.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
AW: common URL encoding/ decoding (base64)
Posted by Korbinian Bachl <ko...@whiskyworld.de>.
well - imnot sure here, but this sounds more an aspect need then a object
one - however, if we would build all urls in a centralised way, at one place
then it might get more easy to set up mor andvanced URL strategys and needs
- e.g: even transport global parameters in restful / bookmarkable URLs
without any special work needed in the particular page(s)
> -----Ursprüngliche Nachricht-----
> Von: Eelco Hillenius [mailto:eelco.hillenius@gmail.com]
> Gesendet: Samstag, 25. November 2006 20:57
> An: wicket-dev@incubator.apache.org
> Betreff: Re: common URL encoding/ decoding (base64)
>
> > some time ago i reportet
> > http://issues.apache.org/jira/browse/WICKET-16
> > , wich was solved fast. However, the problem consits till
> today and so
> > i opened up http://issues.apache.org/jira/browse/WICKET-77
> > These was aimed at the missing decoding of these issues in
> > pageparameters, however, I now wonder if it wouldnt be
> better to give
> > wicket a common URL filter wich decodes and encodes all URLs before
> > they are used/ released so that these are solved forever.
>
> Well, I have been thinking along such lines for different
> reasons, but the problem is the actual implementation. It's
> not that easy to implement while still keeping proper object
> abstractions in place. Of course, if you're able to provide a
> patch that works, I'm sure everyone is interested in looking into it.
>
> Eelco
>
Re: common URL encoding/ decoding (base64)
Posted by Eelco Hillenius <ee...@gmail.com>.
> some time ago i reportet http://issues.apache.org/jira/browse/WICKET-16
> , wich was solved fast. However, the problem consits till today and so i
> opened up http://issues.apache.org/jira/browse/WICKET-77
> These was aimed at the missing decoding of these issues in pageparameters,
> however, I now wonder if it wouldnt be better to give wicket a common URL
> filter wich decodes and encodes all URLs before they are used/ released so
> that these are solved forever.
Well, I have been thinking along such lines for different reasons, but
the problem is the actual implementation. It's not that easy to
implement while still keeping proper object abstractions in place. Of
course, if you're able to provide a patch that works, I'm sure
everyone is interested in looking into it.
Eelco