Re: Wicket 6.4.0 Session/URL bug?

2012-12-21 Thread Martijn Dashorst 
On Fri, Dec 21, 2012 at 1:41 AM, Chris Colman
 wrote:
> Oh, I didn't realize there was a separate ASF based repository.

That is the canonical one. The github ones were just mirrors. "If it
ain't at Apache it isn't Apache™"

> It there a manual (human) based process for changes migrating from the
> ASF repos to the github one or is it automated?

It is automated, but fails fairly often. And it is just triggered once a day.

Martijn

-
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?

2012-12-20 Thread Chris Colman 
Oh, I didn't realize there was a separate ASF based repository.

It there a manual (human) based process for changes migrating from the
ASF repos to the github one or is it automated?

Regards,
Chris

>-Original Message-
>From: Martijn Dashorst [mailto:martijn.dasho...@gmail.com]
>Sent: Thursday, 20 December 2012 6:42 PM
>To: users@wicket.apache.org
>Subject: Re: Wicket 6.4.0 Session/URL bug?
>
>Don't use github if you want the changes right now, it is not the
canonical
>repository. Our ASF based one is. The github repo can be behind for
days.
>
>Martijn
>
>Sent from my iPad
>
>On 19 dec. 2012, at 20:31, "Chris Colman"

>wrote:
>
>> Jira says this has been fixed but I can't, as yet, see any changed on
>> github master branch that have any core code changes that may have
fixed
>> this.
>>
>> Are the changes still in progress?
>>
>> Chris
>>
>>> -Original Message-
>>> From: Jesus Mireles [mailto:toxi...@gmail.com]
>>> Sent: Thursday, 20 December 2012 3:20 AM
>>> To: users@wicket.apache.org
>>> Subject: 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 
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-
>>> 4920<https://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.org>> unsubscr...@wicket.apache.org>
>>>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
--**--**
>> -
>>>> To unsubscribe, e-mail:
users-unsubscribe@wicket.**apache.org>> unsubscr...@wicket.apache.org>
>>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>
>-
>To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>For additional commands, e-mail: users-h...@wicket.apache.org


-
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?

2012-12-20 Thread Bertrand Guay-Paquet 

I confirm that this fixes my problem too. thanks!

On 19/12/2012 2:55 PM, Sven Meier wrote:
https://github.com/apache/wicket/commit/12ce76d17e2d0576fee8158b7fa7db69770bea52 



Sven

On 12/19/2012 08:31 PM, Chris Colman wrote:

Jira says this has been fixed but I can't, as yet, see any changed on
github master branch that have any core code changes that may have fixed
this.

Are the changes still in progress?

Chris


-Original Message-
From: Jesus Mireles [mailto:toxi...@gmail.com]
Sent: Thursday, 20 December 2012 3:20 AM
To: users@wicket.apache.org
Subject: 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  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-

4920<https://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.org
unsubscr...@wicket.apache.org>

For additional commands, e-mail: users-h...@wicket.apache.org





--**--**
-

To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org
unsubscr...@wicket.apache.org>

For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
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?

2012-12-19 Thread Martijn Dashorst 
Don't use github if you want the changes right now, it is not the canonical 
repository. Our ASF based one is. The github repo can be behind for days.

Martijn

Sent from my iPad

On 19 dec. 2012, at 20:31, "Chris Colman"  wrote:

> Jira says this has been fixed but I can't, as yet, see any changed on
> github master branch that have any core code changes that may have fixed
> this.
> 
> Are the changes still in progress?
> 
> Chris
> 
>> -Original Message-
>> From: Jesus Mireles [mailto:toxi...@gmail.com]
>> Sent: Thursday, 20 December 2012 3:20 AM
>> To: users@wicket.apache.org
>> Subject: 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  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-
>> 4920<https://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.org> unsubscr...@wicket.apache.org>
>>>> For additional commands, e-mail: users-h...@wicket.apache.org
> --**--**
> -
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org> unsubscr...@wicket.apache.org>
>>> For additional commands, e-mail: users-h...@wicket.apache.org
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
> 

-
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?

2012-12-19 Thread Sven Meier 

https://github.com/apache/wicket/commit/12ce76d17e2d0576fee8158b7fa7db69770bea52

Sven

On 12/19/2012 08:31 PM, Chris Colman wrote:

Jira says this has been fixed but I can't, as yet, see any changed on
github master branch that have any core code changes that may have fixed
this.

Are the changes still in progress?

Chris


-Original Message-
From: Jesus Mireles [mailto:toxi...@gmail.com]
Sent: Thursday, 20 December 2012 3:20 AM
To: users@wicket.apache.org
Subject: 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  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-

4920<https://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.org
unsubscr...@wicket.apache.org>

For additional commands, e-mail: users-h...@wicket.apache.org





--**--**
-

To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org
unsubscr...@wicket.apache.org>

For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
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?

2012-12-19 Thread Chris Colman 
Got the changes now, thanks Sven!

>-Original Message-
>From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
>Sent: Thursday, 20 December 2012 6:32 AM
>To: users@wicket.apache.org
>Subject: RE: Wicket 6.4.0 Session/URL bug?
>
>Jira says this has been fixed but I can't, as yet, see any changed on
>github master branch that have any core code changes that may have
fixed
>this.
>
>Are the changes still in progress?
>
>Chris
>
>>-Original Message-
>>From: Jesus Mireles [mailto:toxi...@gmail.com]
>>Sent: Thursday, 20 December 2012 3:20 AM
>>To: users@wicket.apache.org
>>Subject: 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  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-
>>4920<https://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.org>unsubscr...@wicket.apache.org>
>>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>>
>>>>
>>>
>>>
>--**--**---
-
>-
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org>unsubscr...@wicket.apache.org>
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>>
>
>-
>To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>For additional commands, e-mail: users-h...@wicket.apache.org


-
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?

2012-12-19 Thread Chris Colman 
Jira says this has been fixed but I can't, as yet, see any changed on
github master branch that have any core code changes that may have fixed
this.

Are the changes still in progress?

Chris

>-Original Message-
>From: Jesus Mireles [mailto:toxi...@gmail.com]
>Sent: Thursday, 20 December 2012 3:20 AM
>To: users@wicket.apache.org
>Subject: 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  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-
>4920<https://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.orgunsubscr...@wicket.apache.org>
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>>
>>
>>
--**--**
-
>> To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.orgunsubscr...@wicket.apache.org>
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>

-
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?

2012-12-19 Thread Bertrand Guay-Paquet 
To be clear, I don't use wicket's auth module. I suspect that what was 
reported is caused by stateful/stateless pages.


On 19/12/2012 12:51 PM, Bertrand Guay-Paquet wrote:

Hi,

I'm trying 6.4.0 now and seeing the same issue.

My use-case is a little bit different though:
1) Without active session, go to stateless page
2) Go to stateful page

The first stateful page loaded is wrong like so:
http://localhost:8080/SERVLET_CONTEXT/SERVLET_CONTEXT;jsessionid=7C9C4B53381D6ADFF82D4DD14CB24630 



Notice the repetition of SERVLET_CONTEXT which is not good and the 
appended jsessionid. Navigating to any other page afterwards works fine.


Regards,
Bertrand

On 19/12/2012 11:19 AM, Jesus Mireles wrote:

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  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-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.org

For additional commands, e-mail: users-h...@wicket.apache.org


--**--**- 

To unsubscribe, e-mail: 
users-unsubscribe@wicket.**apache.org

For additional commands, e-mail: users-h...@wicket.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
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?

2012-12-19 Thread Bertrand Guay-Paquet 

Hi,

I'm trying 6.4.0 now and seeing the same issue.

My use-case is a little bit different though:
1) Without active session, go to stateless page
2) Go to stateful page

The first stateful page loaded is wrong like so:
http://localhost:8080/SERVLET_CONTEXT/SERVLET_CONTEXT;jsessionid=7C9C4B53381D6ADFF82D4DD14CB24630

Notice the repetition of SERVLET_CONTEXT which is not good and the 
appended jsessionid. Navigating to any other page afterwards works fine.


Regards,
Bertrand

On 19/12/2012 11:19 AM, Jesus Mireles wrote:

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  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-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.org
For additional commands, e-mail: users-h...@wicket.apache.org



--**--**-
To unsubscribe, e-mail: 
users-unsubscribe@wicket.**apache.org
For additional commands, e-mail: users-h...@wicket.apache.org





-
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?

2012-12-19 Thread Jesus Mireles 
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  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-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.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
> --**--**-
> To unsubscribe, e-mail: 
> users-unsubscribe@wicket.**apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: Wicket 6.4.0 Session/URL bug?

2012-12-18 Thread Sven Meier 

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-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-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
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?

2012-12-18 Thread Chris Colman 
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-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-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org