[wp-trac] [WordPress Trac] #40164: Apace HTTP 414 error on deleting comments in bulk

[WordPress Trac]

#40164: Apace HTTP 414 error on deleting comments in bulk
---------------------------+-----------------------------
 Reporter:  garethgillman  |      Owner:
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Comments       |    Version:  4.7.3
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+-----------------------------
 Bit of an edge case, but I just had to delete 3000 comments from a WP site
 I took on and I was doing them in 200's (so not to over run the server and
 so I can check for any legitimate comments).

 Doing this, the first 200 comments were "spanmmed" fine, but then you do
 the next 200, it generates a 414 error as the url becomes something like:


 {{{
 /wp-admin/edit-
 comments.php?s=&comment_status=moderated&pagegen_timestamp=2017-03-15+15%3A31%3A06&_total=200&_per_page=200&_page=1&paged=1&_ajax_fetch_list_nonce=ef4afc8347&_wp_http_referer
 =%2Fnew-site%2Fwp-admin%2Fedit-
 comments.php%3Fcomment_status%3Dmoderated%26paged%3D1%26spammed%3D200%26ids%3D814%2C365%2C2177%2C813%2C2021%2C812&_wpnonce=461233332d&_wp_http_referer
 =%2Fnew-site%2Fwp-admin%2Fedit-
 comments.php%3Fcomment_status%3Dmoderated%26paged%3D1%26spammed%3D200%26ids%3D814%2C365%2C2177%2C813
 }}}


 Basically for every process it duplicates the url and if you have 100+
 ID's in each request, it passes a really long url string

 1) Is there a reason why all the comment ID's are passed to the url?
 2) Can this be amended so in edge cases, so the 414 error isn't generated
 as it can and will frustrate some people.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/40164>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform