You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In GemStone 3.3 and 3.4 (at least) when using JQAjax >> script: withOUT the line "self cache: true" (which is the current latest state of seaside), the AJAX URLs are generated with something like this:
It seems to be a problem in the query parsing code in WAUr>>#parseQuery:from:to:
It doesn't check if the nameEnd is less than the parameterEnd, only the queryEnd. So when an unnamed query parameter isn't last in the series of queries (like the callback parameter that precedes the cache busting parameter) then things aren't parsed properly.
In GemStone 3.3 and 3.4 (at least) when using JQAjax >> script: withOUT the line "self cache: true" (which is the current latest state of seaside), the AJAX URLs are generated with something like this:
When in
requestUrlFor:
we parse the URL we get bad results:When that should have been:
It seems to be a problem in the query parsing code in
WAUr>>#parseQuery:from:to:
It doesn't check if the nameEnd is less than the parameterEnd, only the queryEnd. So when an unnamed query parameter isn't last in the series of queries (like the callback parameter that precedes the cache busting parameter) then things aren't parsed properly.
I will see if I can make a PR soon.
The text was updated successfully, but these errors were encountered: