Re: OT: good java hosting
I've been using myhosting.com. I'm not going to claim they are the greatest, but I havent had problems with uptime, speed or price. I stick to custom VPS. On Thu, Jan 16, 2014 at 1:58 PM, Brown, Berlin [PRI-1PP] berlin.br...@primerica.com wrote: It is a little pricey. But I prefer linode for virtual hosting. And they have good docs on tomcat configuration -Original Message- From: Ernesto Reinaldo Barreiro [mailto:reier...@gmail.com] Sent: Thursday, January 16, 2014 9:55 AM To: users@wicket.apache.org Subject: Re: OT: good java hosting Dank je wel! On Thu, Jan 16, 2014 at 3:52 PM, Thomas Matthijs li...@selckin.be wrote: hetzner.de On Thu, Jan 16, 2014 at 3:50 PM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: Danje wel, Bijvoorbeeld? Thanks! On Thu, Jan 16, 2014 at 3:43 PM, Thomas Matthijs li...@selckin.be wrote: On Thu, Jan 16, 2014 at 2:54 PM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: Apologies for the OT message... but I value the opinion of people in this list. Can you suggest a good place to host Wicket applications? I'm hosting a couple of them somewhere I'm NOT very satisfied with service provided. I started to compare offers myself... but a bit of help on that direction will be appreciated. 1- Applications are not very resource/traffic intensive. 2- Quality of support/up time should be good. 3- Just need any relational database. A cheapish dedicated server might be ideal for this, (and way cheaper then anything that even hits at cloud) For 50eur/month you can have 32gb ram quad core i7s mvg, -- Regards - Ernesto Reinaldo Barreiro -- Regards - Ernesto Reinaldo Barreiro - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket 6.4.0 Session/URL bug?
I have uploaded a quickstart and created a new issue: https://issues.apache.org/jira/browse/WICKET-4935 Something interesting, if I dont mount any pages, it works as expected. I was only able to recreate when I actually used mountPackage to mount the private page. Thanks, Jesus M. On Wed, Dec 19, 2012 at 12:41 AM, Sven Meier s...@meiers.net wrote: Hi Nick, WICKET-4920 might be related. Please create a quickstart showing the problem. Thanks Sven On 12/19/2012 06:39 AM, Chris Colman wrote: I have seen this exact same issue. I first saw it after I reported the, possibly related, bug: https://issues.apache.org/**jira/browse/WICKET-4920https://issues.apache.org/jira/browse/WICKET-4920 and then was verifying that it was fixed. I only noticed the bug you describe after I built with a version of Wicket that included the above fix. I'm not saying this fix caused the bug but I never noticed the issue described below until this fix was implemented. Regards, Chris -Original Message- From: Jesus Mireles [mailto:toxi...@gmail.com] Sent: Wednesday, 19 December 2012 1:52 PM To: users@wicket.apache.org Subject: Wicket 6.4.0 Session/URL bug? I'm seeing some strange behavior with the initial launch of a fresh session. I have 3 types of pages which are public, user which is locked down with AuthorizeInstantiation(USER)**, and admin which locked down with AuthorizeInstantiation(ADMIN**). My public pages are using mountPackage and are mounted to root /, my user are mounted to /home and my admin are /admin. I'm using AuthenticatedWebApplication. When I have a clean browser and I hit my application at localhost:8080/ everything works fine and actually if I hit any public page the application works fine and all pages work as expected. However, if the first page is one of the private pages such as localhost:8080/user/Main or localhost:8080/admin/Console then i get forwarded to localhost:8080//Login;**jesssionid=blah. The extra / gives a 404. I can recreate by clearing my browser and starting a new session. Again this only happens if the first page I hit is one of those private pages otherwise the forward to the login works as expected and I dont get a 404. This only happens with the latest 6.4.0 release. Any ideas? Thanks! Jesus M. --**--**- To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org --**--**- To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Wicket 6.4.0 Session/URL bug?
I'm seeing some strange behavior with the initial launch of a fresh session. I have 3 types of pages which are public, user which is locked down with AuthorizeInstantiation(USER), and admin which locked down with AuthorizeInstantiation(ADMIN). My public pages are using mountPackage and are mounted to root /, my user are mounted to /home and my admin are /admin. I'm using AuthenticatedWebApplication. When I have a clean browser and I hit my application at localhost:8080/ everything works fine and actually if I hit any public page the application works fine and all pages work as expected. However, if the first page is one of the private pages such as localhost:8080/user/Main or localhost:8080/admin/Console then i get forwarded to localhost:8080//Login;jesssionid=blah. The extra / gives a 404. I can recreate by clearing my browser and starting a new session. Again this only happens if the first page I hit is one of those private pages otherwise the forward to the login works as expected and I dont get a 404. This only happens with the latest 6.4.0 release. Any ideas? Thanks! Jesus M.
