Alex, this was a great help, thank you!
On Thu, Dec 17, 2009 at 3:23 PM, Alex Objelean alex_objel...@yahoo.comwrote:
Though I didn't use it, there is HttpsRequestCycleProcessor (you should add
it in your Application) and @RequireHttps annotation (for each WebPage
which
must be accessed
Thanks Alex.
I just had another meeting w/ the SEO guy today and the idea is to track
orders moving through our storefront in order go gauge sales based on the
SEO strategy. In other words, where did our customers come from (Google
search?), what did they buy, and did they make it all the way
Subject: Re: Pretty URLs and sessions
Thanks Alex.
I just had another meeting w/ the SEO guy today and the idea is to track
orders moving through our storefront in order go gauge sales based on the
SEO strategy. In other words, where did our customers come from (Google
search?), what did they buy
There are two possibilities:
1) In your application class add the following:
mount(new HybridUrlCodingStrategy(/checkout, CheckoutPage.class));
2) If you have wicket-stuff annotation dependency
(http://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-annotation)
you can annotate your
Also, it could be useful to check this out:
http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html
Alex
V. Jenks wrote:
Excellent, excellent! This is exactly what I was after! That is...unless
this SEO can find another monkey wrench to throw in it. But...it
Hit a snag! At the cart page (going into the login page), I redirect to
https like so:
getRequestCycle().setRedirect(false);
getRequestCycle().setRequestTarget(EmptyRequestTarget.getInstance());
getResponse().redirect(https://mysite/app/account;);
user-account being mapped
everything that goes on. Everything they clicked, how long they spent where,
you can even track where their mouse was hovering! ;)
- Alex R.
-Original Message-
From: VGJ [mailto:zambi...@gmail.com]
Sent: Thursday, December 17, 2009 4:08 PM
To: users@wicket.apache.org
Subject: Re: Pretty URLs
You shouldn't have a code like this:
getRequestCycle().setRedirect(false);
getRequestCycle().setRequestTarget(EmptyRequestTarget.getInstance());
getResponse().redirect(
https://mysite/app/?wicket:bookmarkablePage=:com.myapp.UserAccount;);
A more 'wicket way' of doing thins
Yes I know, I do this most of the time. However, I'm redirecting from http
to https. When I wrote this app, this was what everyone was recommending.
Is there another way?
On Thu, Dec 17, 2009 at 2:45 PM, Alex Objelean alex_objel...@yahoo.comwrote:
You shouldn't have a code like this:
Though I didn't use it, there is HttpsRequestCycleProcessor (you should add
it in your Application) and @RequireHttps annotation (for each WebPage which
must be accessed through SSL) which should make this work.
Alex
V. Jenks wrote:
Yes I know, I do this most of the time. However, I'm
I'm working on some changes for our storefront (Wicket 1.4, Java EE 5,
Glassfish 2.1) based on some recommendations made to us by an SEO
consultant. One of them is re-writing some of the URLs so as to have them
indexed by Google, etc.
My concern is the Wicket WebSession that I use to pass around
11 matches
Mail list logo
