Re: POST path via Ajax erratically invalid when used with #

2011-05-02 Thread Jeremy Levy
It happens consistently in Chrome and the fix is to clear cookies / JSESSIONID... Can you be more specific in the javascript where the relative path is assembled I can't find it... ? On Fri, Apr 29, 2011 at 3:10 AM, Martin Grigorov mgrigo...@apache.orgwrote: See wicketSubmitFormById() and

Re: POST path via Ajax erratically invalid when used with #

2011-05-02 Thread Martin Grigorov
I am not aware of any logic in wicket-ajax.js which changes the url passed from the server side. See org.apache.wicket.ajax.AjaxEventBehavior.generateCallbackScript(CharSequence) I gave you the names of the JavaScript functions which trigger the form submit. Use Chrome Developer Tools to debug

Re: POST path via Ajax erratically invalid when used with #

2011-05-02 Thread Jeremy Levy
Thanks for the reply, as I already mentioned I've tried running this in the debugger in Chrome but it's not clear to me where the HOST part of the URL is being generated all I see is the path. The full URL that is getting posted to is:

Re: POST path via Ajax erratically invalid when used with #

2011-04-29 Thread Martin Grigorov
See wicketSubmitFormById() and wicketAjaxPost() in wicket-ajax.js On Fri, Apr 29, 2011 at 12:59 AM, Jeremy Levy jel...@gmail.com wrote: I've noticed that in 1.4.17 in some circumstances when using Wicket to POST data over AJAX the path it's POSTing to tries to include the value after # in the

POST path via Ajax erratically invalid when used with #

2011-04-28 Thread Jeremy Levy
I've noticed that in 1.4.17 in some circumstances when using Wicket to POST data over AJAX the path it's POSTing to tries to include the value after # in the URL. For example on a page with a URL like http://foo.bar/MyPage#one Wicket-Ajax attempts to POST to http://foo.bar/MyPageone. I'm having

Re: POST path via Ajax erratically invalid when used with #

2011-04-28 Thread Clint Checketts
I don't know which method, but I am curious which browser you are seeing it in. On Thu, Apr 28, 2011 at 4:59 PM, Jeremy Levy jel...@gmail.com wrote: I've noticed that in 1.4.17 in some circumstances when using Wicket to POST data over AJAX the path it's POSTing to tries to include the value