Re: ListenerRequestHandler / urls from the past... - component not found

2018-06-30 Thread Korbinian Bachl
Thanks for the answer - that gives me the right direction. Say, do you know if it would be possible to have the wicket component part not in the url like currently but using a named parameter? e.g.: http://examples7x.wicket.apache.org/forminput/?0-1.IFormSubmitListener-inputForm should instead

Re: ListenerRequestHandler / urls from the past... - component not found

2018-06-30 Thread Sven Meier
Hi, >http://examples7x.wicket.apache.org/forminput/?0-1.IFormSubmitListener-inputForm "0-1.IFormSubmitListener-inputForm" *is* a parameter, it just doesn't have a value. How would renaming that parameter improve anything? Have fun Sven Am 30.06.2018 um 12:06 schrieb Korbinian Bachl: Thank

Re: ListenerRequestHandler / urls from the past... - component not found

2018-06-30 Thread Korbinian Bachl
Hi Sven, well, the problem here are our clever webbots - especially bing and even worse google :) See, bingbot or googlebot index now e.g.: (derived from wicket examples) www.domain.com/choice and a load of bullshit like choice?2-1.IBehaviorListener.0-form-makes choice?2-1.IBehaviorListener

Re: ListenerRequestHandler / urls from the past... - component not found

2018-06-30 Thread Bas Gooren
Hi! Well that’s something you can fix by embedding a canonical url in your page. It tells search engines to ignore all other urls for that page, including the ones with wicket info in them. // Bas Verstuurd vanaf mijn iPhone > Op 30 jun. 2018 om 19:41 heeft Korbinian Bachl > het volgende gesc

Re: ListenerRequestHandler / urls from the past... - component not found

2018-06-30 Thread Korbinian Bachl
Yeah - no; the problem is here the amount of pages and the crawl-budget of a crawler per domain; If you waste 1000's of urls you get not indexed well enough and even penalized; I know this and we use canonical all over the places, but seo guys clearly showed that we need to get rid of this and