E
egarcia
Guest
Hello, The screenshot that you included shows that the value of JSESSIONID has the text for the filter. Notice that the string has ";" instead of "&" to separate the values. This makes the two parts be the value for JSESSIONID, instead of recognizing filter as a separate parameter. I believe that there is a bug logged. Is your intention to have JSESSIONID in the URL? (I am guessing you might be doing this to share the session for AJAX calls but I am not sure.) The issue with the filter does not occur if JSESSIONID is passed as an HTTP only cookie which is the default. Please let us know how this impact you. Perhaps, you would be ok using a custom version of the library with a fix. I hope this helps. P.S; For those looking for an example: oemobiledemo.progress.com/.../example014b.html shows the usage of the filter option.
Continue reading...
Continue reading...