Wicket form submits, FBML and redirects has been created by Lauri Lehtinen (May 22, 2008).

Content:

Today I struggled with more redirect related issues as I continued rewriting our Facebook app with Wicket - I'll note my observations here (keep in mind that I am a first-timer with Wicket).

When I submit one of my forms, my access log reveals that Wicket follows the "redirect after post" pattern.

"POST /appcontext/somepage?wicket:interface=:0:somepanel:someform::IFormSubmitListener:: HTTP/1.1" 200
"POST /appcontext/somepage?wicket:interface=:1:::: HTTP/1.1" 200

In the context of a Facebook FBML application, the second access log entry never appears, and the url in the browser remains as follows:

http://apps.facebook.com/myapp/somepage?wicket:interface=:0:somepanel:someform::IFormSubmitListener::

which seems to represent some expired state of the page. If one does a refresh on the page, the browser's "repost popup" appears, and if one chooses to resubmit the form, Wicket responds with a 404 - Page expired.

This is by Facebook's design and the redirect issued by Wicket after the form post is simply ignored and never makes it to the browser. Access log looks like this:

"POST /appcontext/somepage?wicket:interface=:0:somepanel:someform::IFormSubmitListener:: HTTP/1.1" 200

Reply via email to