Added this field and notice that it writes additional params to the
url for pagemap.
Preliminary testing indicated that the page map url parameter doesn't
have to exist.
Are there any concerns with using this option?
Douglas
On Oct 1, 2009, at 7:14 PM, Douglas Ferguson wrote:
What are
Are there no pros and cons of using this?
On Oct 2, 2009, at 11:39 AM, Douglas Ferguson wrote:
Added this field and notice that it writes additional params to the
url for pagemap.
Preliminary testing indicated that the page map url parameter doesn't
have to exist.
Are there any concerns
What are the implications of turning this one?
D/
On Sep 30, 2009, at 1:23 AM, Igor Vaynberg wrote:
the javadoc in the later versions mentions that it is enabled by
default, however if you are using the default secondlevel caching page
store it will be disabled...
-igor
On Tue, Sep 29,
hi,
actually i'm able to make it work some how using this setting
getPageSettings().setAutomaticMultiWindowSupport(true);
it creates a new page map everytime i open a page in a new tab or new window.
however in the wicket documentation it says that it is enabled by
default. but upon checking it
the javadoc in the later versions mentions that it is enabled by
default, however if you are using the default secondlevel caching page
store it will be disabled...
-igor
On Tue, Sep 29, 2009 at 11:10 PM, Carlo Camerino
carlo.camer...@gmail.com wrote:
hi,
actually i'm able to make it work
Hi everyone,
We have this requirement in which we cannot allow the customer to copy
paste the url that's appearing in the address bar into the same
browser. For example in a different tab or in a new window. This can
easily be done in Wicket Framework since the url has a corresponding
page
We have this requirement in which we cannot allow the customer to copy
paste the url that's appearing in the address bar into the same
browser.
Crazy thing. How about to include an request counter to your url
encode/decode strategy?
On Tue, Sep 29, 2009 at 1:41 PM, Carlo Camerino
On Tue, Sep 29, 2009 at 6:48 PM, Pedro Santos pedros...@gmail.com wrote:
We have this requirement in which we cannot allow the customer to copy
paste the url that's appearing in the address bar into the same
browser.
Crazy thing. How about to include an request counter to your url
could'nt he just have a page map with a size of 0? Of course reloads
would'nt work and probably a bunch of other stuff too.. Seems like at
strange thing to limit on though.
2009/9/29 Matej Knopp matej.kn...@gmail.com
On Tue, Sep 29, 2009 at 6:48 PM, Pedro Santos pedros...@gmail.com wrote:
We
ya it's sort of our requirement i don't think i would set my pagemap to 0.
i'm thinking of a control i could use in order to determine that this
page is accessed. i'm thinking of the best way to do it though.
i could maybe include a hidden field in each of my form that i have to
check each
I'm guessing they are trying to limit users from taking a test in one window
and seeing the previous answers in another.
-Clint
On Tue, Sep 29, 2009 at 12:29 PM, nino martinez wael
nino.martinez.w...@gmail.com wrote:
could'nt he just have a page map with a size of 0? Of course reloads
Ahh good example for usage :)
2009/9/29 Clint Checketts checke...@gmail.com
I'm guessing they are trying to limit users from taking a test in one
window
and seeing the previous answers in another.
-Clint
On Tue, Sep 29, 2009 at 12:29 PM, nino martinez wael
nino.martinez.w...@gmail.com
Okay in that case you should be able to use some of the stuff that are used
in apps that are supposed be *cross*-*site* request *forgery proof*, search
the list for that.
2009/9/29 Carlo Camerino carlo.camer...@gmail.com
ya it's sort of our requirement i don't think i would set my pagemap
Your options here are rather limited. Wicket or not, it is still a web
application. HTTP is a stateless protocol. There are ways/hacks to
detect opening page in new window/tab but they require javascript and
are not 100% bullet proof. If you need real solution for this forget
about web
I am not aware that Wicket has direct support for this kind of
(mis-)behavior.
You can, however employ some kind of cheating here. if you set the http
headers to no-cache with the help of a servlet filter, the browser will
not allow the page to be copy-pasted from local cache, and will
What happens if the user (perhaps accidentally) refreshes page?
-Matej
On Tue, Sep 29, 2009 at 11:43 PM, Andreas Petersson
andr...@petersson.at wrote:
I am not aware that Wicket has direct support for this kind of
(mis-)behavior.
You can, however employ some kind of cheating here. if you set
Matej Knopp schrieb:
What happens if the user (perhaps accidentally) refreshes page?
-Matej
he would get an error page using the described approach. clearly not
what you would want in a general-purpose web app.
BR
Andreas
-
2009/9/29 Carlo Camerino carlo.camer...@gmail.com:
Hi everyone,
We have this requirement in which we cannot allow the customer to copy
paste the url that's appearing in the address bar into the same
browser. For example in a different tab or in a new window. This can
easily be done in Wicket
18 matches
Mail list logo
