
|
If you were logged in you would be able to see more operations.
|
|
|
|
When there are parameters in the requestURI property of <display:table>, there are indefinitely concatenated at each sorting, paging ...
For example if my property is defined as :
requestURI="/foo/bar.do?method=search"
after three sorting my URL looks like
/foo/bar.do?d-49653-o=2&d-49653-p=1&d-49653-s=1&method=search&method=search&method=search&method=search
More serious, if my first URL is something like "/foo/bar.do?method=init", the requestURI has no effect, since the URL looks like
/foo/bar.do?d-49653-o=2&d-49653-p=1&d-49653-s=1&method=init&method=search
and my parameter method=search is not taken ...
|
|
Description
|
When there are parameters in the requestURI property of <display:table>, there are indefinitely concatenated at each sorting, paging ...
For example if my property is defined as :
requestURI="/foo/bar.do?method=search"
after three sorting my URL looks like
/foo/bar.do?d-49653-o=2&d-49653-p=1&d-49653-s=1&method=search&method=search&method=search&method=search
More serious, if my first URL is something like "/foo/bar.do?method=init", the requestURI has no effect, since the URL looks like
/foo/bar.do?d-49653-o=2&d-49653-p=1&d-49653-s=1&method=init&method=search
and my parameter method=search is not taken ... |
Show » |
Sort Order:
|
We are also seeing the same issue of adding unwanted parameters to the requestURI.
Pls suggest me whether this bug has fixed in later version or not?
Thanks In Advance