What steps will reproduce the problem?
1. View a report, client uses a GET request, not a POST
2. POST is slightly more secure in that it "hides" parameters from browser
history, access logs, etc
What is the expected output? What do you see instead?
1. Use POST instead of GET
Right now this is low priority because there aren't any unique parameters
passed to the reports yet, because they don't accept custom parameters. Once
they do, and that data is potentially sensitive in a future release, this will
be more important.
Original issue reported on code.google.com by joshdrum...@gmail.com on 9 Dec 2010 at 3:42
Original issue reported on code.google.com by
joshdrum...@gmail.com
on 9 Dec 2010 at 3:42