hi, thanks for your reply. we de-activated cookies within container and are using JSESSIONID as URL Parameter (otherwise our user/session management would not work either).
-> the proxy filter principally works on a protocol level and is passing 100% of the request content (besides one replaced content, not wicket related), so technically it should work, or how is wicket able to detect, if a form post is coming from a certain browser? -> i assume, the problem is related to the way we are building the method action : in a "normal" wicket form the action url is looking like this : ./de.package.Page?9-1.IFormSubmitListener-form -> since we have to modify this method url it looks like https://3dparty:9999/our_context/wicket/bookmarkable/de.package.Page;jsessionid=69FCA354DA44DEB83B97A717FAA2A332?3-1.IFormSubmitListener-form i don't think this hack is correct (even if bean is called at least with constructor call) - what would be the correct way to build up the method action on our own using a absolute url? kind regards -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-FormPost-via-ProxyFilter-tp4665803p4665806.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
