OK, how can I help? On Wed, Nov 23, 2016 at 3:40 PM, Martin Grigorov <mgrigo...@apache.org> wrote:
> See https://issues.apache.org/jira/browse/WICKET-6056 > It is almost possible to extend the BrowserInfoPage. It needs just little > more work. > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Tue, Nov 22, 2016 at 7:02 PM, Maxim Solodovnik <solomax...@gmail.com> > wrote: > > > Does it make any sense? > > > > On Tue, Nov 22, 2016 at 10:25 AM, Maxim Solodovnik <solomax...@gmail.com > > > > wrote: > > > > > And maybe protocol+context (or window.location.href) :) > > > mod_proxy, mod_rewrite can change the URL a lot :) > > > > > > On Tue, Nov 22, 2016 at 10:18 AM, Maxim Solodovnik < > solomax...@gmail.com > > > > > > wrote: > > > > > >> Hello All, > > >> > > >> I wonder is there any way to extend gathered org.apache.wicket.pro > > >> tocol.http.ClientProperties? > > >> I would like to have port in addition to hostname > > >> Or maybe I can provide PR to wicket so it would have this info by > > default? > > >> > > >> WDYT? > > >> > > >> -- > > >> WBR > > >> Maxim aka solomax > > >> > > > > > > > > > > > > -- > > > WBR > > > Maxim aka solomax > > > > > > > > > > > -- > > WBR > > Maxim aka solomax > > > -- WBR Maxim aka solomax
