Vote #78114
未完了Use POST to export Issue query results to CSV instead of GET
0%
説明
When trying to export issues to CSV, all request params (filter settings) are sent in the URL via a GET request. For an issue filter with lots of params using non-latin characters it is quite easy to hit the 8190 byte URL length limit for apache2.
I suppose it'd be better to send POST requests with params sent as request body thus allowing to manage larger amounts of data.
journals
I am against this (I usually use non-latin characters, Japanese).
If this feature is implemented, we will not be able to tell the URL of filtered issues list via email or chat like this:
http://www.redmine.org/projects/redmine/issues?utf8=%E2%9C%93&set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&f%5B%5D=subject&op%5Bsubject%5D=%7E&v%5Bsubject%5D%5B%5D=Use+POST&f%5B%5D=tracker_id&op%5Btracker_id%5D=%3D&v%5Btracker_id%5D%5B%5D=2&f%5B%5D=&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=subject&c%5B%5D=updated_on&c%5B%5D=category&group_by=
--------------------------------------------------------------------------------
I think the OP is using a saved query and just has the problem that the modal CSV export options form serializes the query (even if it is a stored query) into a bunch of hidden fields for filters and options etc. If the modal would instead just use a hidden @query_id@ field he wouldn't have the problem. Or if the options form in the modal (and just this) would use POST.
--------------------------------------------------------------------------------