You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "bernard (JIRA)" <ji...@apache.org> on 2010/08/26 11:00:58 UTC

[jira] Commented: (WICKET-3000) Panel Replacement does not work without Browser Cookie Support

    [ https://issues.apache.org/jira/browse/WICKET-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902787#action_12902787 ] 

bernard commented on WICKET-3000:
---------------------------------

Many thanks Igor for your quick repy.

I have filed a GlassFish issue for this:

https://glassfish.dev.java.net/issues/show_bug.cgi?id=13129
Session is null in request with URL containing jsessionid parameter


> Panel Replacement does not work without Browser Cookie Support
> --------------------------------------------------------------
>
>                 Key: WICKET-3000
>                 URL: https://issues.apache.org/jira/browse/WICKET-3000
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.10
>         Environment: GlassFish 3.01, FireFox 3.6.3
>            Reporter: bernard
>            Assignee: Igor Vaynberg
>         Attachments: PanelReplacement.zip
>
>
> Please excuse my ignorance if this is not generally supported.
> I switched off cookie suport in FireFox 3.6.3 to test whether an application still works via URL rewriting.
> In FireFox Tools|Option|Privacy|History|FireFox will:Use Custom Settings for History|Uncheck "Accept Cookies from Sites"
> With the attached testcase (NetBeans Project without wicket), I get "Page Expired" when trying to replace a panel on the page.
> I am replacing panels all the time, and now I am wondering whether this is at all a good idea, or whether I should require cookies.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.