ajax anti-cache issue in 3.X.X
Given a url (that was, for example, returned from a server after a prior ajax nocache request):
/myapp/?_=1111&nextPage=2
and issuing a new jquery.ajax call with that url and cache=false will cause the request url to be changed to something like:
/myapp/&nextPage=2?_=1112
which causes the request to be unrecognized.
In jquery 3.0.0-alpha1 and prior versions, the ajax anti-cache code did an in-place setting of the anti-cache parameter and updated the url with something like:
/myapp/?_1112&nextPage=2
Starting in 3.0.0-beta1, this was changed to first remove any anti-cache param and then tack the new value on the end without regard to other query params. Seems the anti-cache param should either be updated in place as it used to be, or the url needs to be re-assembled more intelligently than it is now.
/myapp/?_=1111&nextPage=2
and issuing a new jquery.ajax call with that url and cache=false will cause the request url to be changed to something like:
/myapp/&nextPage=2?_=1112
which causes the request to be unrecognized.
In jquery 3.0.0-alpha1 and prior versions, the ajax anti-cache code did an in-place setting of the anti-cache parameter and updated the url with something like:
/myapp/?_1112&nextPage=2
Starting in 3.0.0-beta1, this was changed to first remove any anti-cache param and then tack the new value on the end without regard to other query params. Seems the anti-cache param should either be updated in place as it used to be, or the url needs to be re-assembled more intelligently than it is now.