The query string is literally the string which follows the ? in the url. When you are posting you are not using the query string but instead you are encoding the data in the body of the post which is why it can hold more data. Instead of using getQueryString() then looking for the pieces of that you can use getParameter('name') and it will return the value given with that name and you won't even have to URL decode it. Caleb On 05/18/2011 05:50 PM, China Sunrise wrote:
Hi, My xwiki 3.0 implementation is using PHP in many pages, and some pages are based on simple HTML forms with a "submit" button. In the PHP part, I process $request->getQueryString() to check the form fields that were sent. It works very well when the form used the GET method, but doesn't work at all when the form used the POST method. Doing some research, it looks like the getQueryString() method should handle both scenarios but it doesn't, so I wonder if there is anything else blocking the POST data at a lower level.
I also did the same test not inside PHP and run into the same issue, so it does not look to be PHP-related.
Unfortunately this is becoming critical as GET data size is limited and I start running into this limit on some forms, so have to move to POST.
Thanks _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users