The buffer is empty. I see from the request the querystring is wicket:interface=:7:projectPagePanel:toolBox2:inviteUserPanel:hiddenArea:invitePanel:inviteForm:inviteButton::IActivePageBehaviorListener:0:&wicket:ignoreIfNotActive=true&random=0.2301371863577515
the response is a http 200 adn ther redirectURL is set to ?wicket:interface=:7:::: - not sure if this is relavent. If I can the button to a norml button (not an AjaxButton) it works fine. Looks like I will need to do this. On Mon, Jun 22, 2009 at 1:29 PM, Wayne Pope<[email protected]> wrote: > Yes sorry - apologies to all. > I'll have a look Martin. > > On Mon, Jun 22, 2009 at 1:11 PM, Martin Funk<[email protected]> wrote: >> uh, now that's a moving target. >> >> sorry but no solution out of my head, but next steps for me would be >> checking if it happens on the server or on its way to the browser. >> What does the response Buffer in the WicketFilter look like just before the >> doGet returns? >> >> mf >> Am 22.06.2009 um 12:58 schrieb Wayne Pope: >> >>> It looks like we are using an AjaxButton. >>> Sorry for 2 emails to describe the one problem. >>> Any ideas? >>> >>> many thanks >>> >>> On Mon, Jun 22, 2009 at 12:49 PM, Wayne Pope<[email protected]> >>> wrote: >>>> >>>> Sorry I just realised that its not ajax - just a normal form submit. >>>> We still have the same problem though >>>> >>>> >>>> Wayne Pope-2 wrote: >>>>> >>>>> Hi, >>>>> >>>>> not sure how to investigate this, but we have an issue with ajax and >>>>> safari. Problem is it doesn't happen every time - only about 40% . >>>>> Essentally we send a request: >>>>> >>>>> Request >>>>> Accept text/xml >>>>> Content-Type application/x-www-form-urlencoded >>>>> Referer >>>>> http://foo1.glasscubesdev.com:8080/?wicket:interface=:5:::: >>>>> User-Agent Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) >>>>> AppleWebKit/525.19 (KHTML, like Gecko) Version/3.1.2 Safari/525.21 >>>>> Wicket-Ajax true >>>>> >>>>> We receive this on the server/eclipse and the request is processed. >>>>> However the response is received like this on safari (using the >>>>> developer menu): >>>>> Response >>>>> Ajax-Location ?wicket:interface=:5:::: >>>>> Content-Length 1 >>>>> Server Jetty(6.1.4) >>>>> >>>>> >>>>> As you can see the content length is 1. The effect is that it appears >>>>> that request never returns (there's nothing in the ajax debug window). >>>>> It happens locally and on the server. We're on 1.4-rc2 of wicket. >>>>> >>>>> Any ideas? Anyone seen something like this before? >>>>> >>>>> many thanks >>>>> Wayne >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/AJAX-and-Safari-tp24145113p24145166.html >>>> Sent from the Wicket - User mailing list archive at Nabble.com. >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
