Title: Request Entity Too Large
Last modified: August 30, 2016

---

# Request Entity Too Large

 *  [apkajanu](https://wordpress.org/support/users/apkajanu/)
 * (@apkajanu)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/request-entity-too-large-5/)
 * Hi, We have around 6500 user registered with the website. For some marketing 
   reasons we have to get user’s lists with export to csv option. It was working
   a month ago but now we are getting the following error:
 * “Request Entity Too Large
 * The requested resource
    /wp-admin/users.php does not allow request data with 
   POST requests, or the amount of data provided in the request exceeds the capacity
   limit.”
 * We tried to update php.ini with:
    upload_max_filesize = 225M post_max_size = 
   225M but it doesnt work. Any advice?
 * Regards.
 * [https://wordpress.org/plugins/amr-users/](https://wordpress.org/plugins/amr-users/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [anmari](https://wordpress.org/support/users/anmari/)
 * (@anmari)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/request-entity-too-large-5/#post-6538695)
 * Hi, it seems the size of the CSV is hitting some server limits.
    One approach
   could be to increase those limits. if you do a bit more googling, there are other
   aspects mentioned (I’m NOT expert in server config, i just found a few posts 
   by googling both “Request Entity Too Large” and “the amount of data provided 
   in the request exceeds the capacity limit”) These posts mention a bunch of things
   that could cause it.
 * [http://stackoverflow.com/questions/8896644/request-entity-too-large](http://stackoverflow.com/questions/8896644/request-entity-too-large)
   
   [http://stackoverflow.com/questions/18121227/how-to-avoid-request-entity-too-large-413-error](http://stackoverflow.com/questions/18121227/how-to-avoid-request-entity-too-large-413-error)
 * **OTHER APPROACHES:**
    1) avoid the huge POST form and send CSV to FILE on server
   Are you doing the CSV extract through admin backend on a non public list ? Temporarily
   make the list public (if it’s sensitive data MAKE sure that the list does NOT
   have ‘Show CSV’ ticked in the overview (so it does not present as an option if
   list in front end) On next cache run it will write the csv to a file. Download
   file. Then make the list NOT public – the file will be deleted.
 * 2) OR reduce the size of the data. Are all fields required ?
    Do you have any
   junk users who can be excluded from the list by some criteria ? Maybe break the
   list into sublists by some criteria.
 * See note 1 re large lists on main description near bottom [https://wordpress.org/plugins/amr-users/](https://wordpress.org/plugins/amr-users/)
 * DO please let us know how you for the benefit of any others.

Viewing 1 replies (of 1 total)

The topic ‘Request Entity Too Large’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/amr-users_f6f6f4.svg)
 * [amr users](https://wordpress.org/plugins/amr-users/)
 * [Support Threads](https://wordpress.org/support/plugin/amr-users/)
 * [Active Topics](https://wordpress.org/support/plugin/amr-users/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/amr-users/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/amr-users/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [anmari](https://wordpress.org/support/users/anmari/)
 * Last activity: [10 years, 8 months ago](https://wordpress.org/support/topic/request-entity-too-large-5/#post-6538695)
 * Status: not resolved