Feature #24782

Use POST to export Issue query results to CSV instead of GET

Added by Serghei Zagorinyak over 5 years ago. Updated about 4 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues filter
Target version:-
Resolution:

Description

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.

History

#2 Updated by Jens Krämer about 4 years ago

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.

Also available in: Atom PDF