Download large pivot tables as Excel (414 Request-URI Too Large)

Support - Assistance technique
1

Dear all,

when I try to download some pivot tables as Excel, sometimes I received the error “414 Request-URI Too Large” with large tables (around 2000 rows). Is it possible to solve this?

Thanks

Jose

2

I guess this could be related to your Apache or Nginx setup:
http://stackoverflow.com/questions/2891574/how-do-i-resolve-a-http-414-request-uri-too-long-error

http://stackoverflow.com/questions/1067334/how-to-set-the-allowed-url-length-for-a-nginx-request-error-code-414-uri-too

···

On Mon, Dec 23, 2013 at 5:47 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear all,

when I try to download some pivot tables as Excel, sometimes I received the error “414 Request-URI Too Large” with large tables (around 2000 rows). Is it possible to solve this?

Thanks

Jose

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Knut Staring

Dept. of Informatics, University of Oslo

+4791880522

http://dhis2.org

3

Hi Jose,

thanks for reporting. We are aware of the problem. It usually happens when you select a lot of data elements/indicators, leading to a long GET request string. There is no formal standard here, but various limits are imposed by browsers and web servers, from IE at 2 Kb to Chrome at 100 Kb.

We will look into the case right now and let you know, there might be potential for doing better than we do currently.

Lars

···

On Mon, Dec 23, 2013 at 5:47 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear all,

when I try to download some pivot tables as Excel, sometimes I received the error “414 Request-URI Too Large” with large tables (around 2000 rows). Is it possible to solve this?

Thanks

Jose

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

4

Hi Jose,

we have now made a fix for this. We are now not imposing any restrictions on this inside DHIS, rather trying the request and catching potential error messages from the web server. By using a modern browser this should give you approximately 4 times bigger pivots.

We will back-port to version 2.13 shortly.

regards,

Lars

···

On Mon, Dec 30, 2013 at 11:36 AM, Lars Helge Øverland larshelge@gmail.com wrote:

Hi Jose,

thanks for reporting. We are aware of the problem. It usually happens when you select a lot of data elements/indicators, leading to a long GET request string. There is no formal standard here, but various limits are imposed by browsers and web servers, from IE at 2 Kb to Chrome at 100 Kb.

We will look into the case right now and let you know, there might be potential for doing better than we do currently.

Lars

On Mon, Dec 23, 2013 at 5:47 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear all,

when I try to download some pivot tables as Excel, sometimes I received the error “414 Request-URI Too Large” with large tables (around 2000 rows). Is it possible to solve this?

Thanks

Jose

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

5

Thanks Lars - we look forward in getting this back ported to 2.13, so we can address this asap. We do plan to upgrade to 2.14, but it will take until April to do full testing and prepare release notes (and re training). The changes on the menus and person attributes are big changes for our users.

···

Rodolfo Meliá

*Principal | *rmelia@knowming.com

Skype: rod.melia | +44 777 576 4090 | +1 708 872 7636

www.knowming.com

On Tue, Jan 7, 2014 at 4:13 PM, Lars Helge Øverland larshelge@gmail.com wrote:

Hi Jose,

we have now made a fix for this. We are now not imposing any restrictions on this inside DHIS, rather trying the request and catching potential error messages from the web server. By using a modern browser this should give you approximately 4 times bigger pivots.

We will back-port to version 2.13 shortly.

regards,

Lars

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Mon, Dec 30, 2013 at 11:36 AM, Lars Helge Øverland larshelge@gmail.com wrote:

Hi Jose,

thanks for reporting. We are aware of the problem. It usually happens when you select a lot of data elements/indicators, leading to a long GET request string. There is no formal standard here, but various limits are imposed by browsers and web servers, from IE at 2 Kb to Chrome at 100 Kb.

We will look into the case right now and let you know, there might be potential for doing better than we do currently.

Lars

On Mon, Dec 23, 2013 at 5:47 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear all,

when I try to download some pivot tables as Excel, sometimes I received the error “414 Request-URI Too Large” with large tables (around 2000 rows). Is it possible to solve this?

Thanks

Jose

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

6

Hi Rodolfo,

turns out this was actually back-ported last week.

Lars

···

On Wed, Jan 8, 2014 at 8:59 PM, Rodolfo Melia rmelia@knowming.com wrote:

Thanks Lars - we look forward in getting this back ported to 2.13, so we can address this asap. We do plan to upgrade to 2.14, but it will take until April to do full testing and prepare release notes (and re training). The changes on the menus and person attributes are big changes for our users.

Rodolfo Meliá

*Principal | *rmelia@knowming.com

Skype: rod.melia | +44 777 576 4090 | +1 708 872 7636

www.knowming.com

On Tue, Jan 7, 2014 at 4:13 PM, Lars Helge Øverland larshelge@gmail.com wrote:

Hi Jose,

we have now made a fix for this. We are now not imposing any restrictions on this inside DHIS, rather trying the request and catching potential error messages from the web server. By using a modern browser this should give you approximately 4 times bigger pivots.

We will back-port to version 2.13 shortly.

regards,

Lars

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Mon, Dec 30, 2013 at 11:36 AM, Lars Helge Øverland larshelge@gmail.com wrote:

Hi Jose,

thanks for reporting. We are aware of the problem. It usually happens when you select a lot of data elements/indicators, leading to a long GET request string. There is no formal standard here, but various limits are imposed by browsers and web servers, from IE at 2 Kb to Chrome at 100 Kb.

We will look into the case right now and let you know, there might be potential for doing better than we do currently.

Lars

On Mon, Dec 23, 2013 at 5:47 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear all,

when I try to download some pivot tables as Excel, sometimes I received the error “414 Request-URI Too Large” with large tables (around 2000 rows). Is it possible to solve this?

Thanks

Jose

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

7

Under Apache, the limit is a configurable value, LimitRequestLine. Change this value to something larger than its default of 8190 if you want to support a longer request URI. Extremely long URLs are usually a mistake. If you keep URLs under 2000 characters , they’ll work in virtually any combination of client and server software. URI actually have a character limit depending on several things. Chrome limits url length of 2MB for practical reasons and to avoid causing denial-of-service problems in inter-process communication. On most platforms, Chrome’s omnibox limits URL display to 32kB ( kMaxURLDisplayChars ) although a 1kB limit is used on VR platforms. IE - 2083 characters, Firefox - 2047 characters, Safari 80000 characters and Opera 190,000 characters.

To resolve the problem :

  • By POST request: Convert query string to json object and sent to API request with POST

  • By GET request: Max length of request is depend on sever side as well as client side. Most webserver have limit 8k which is configurable. On the client side the different browser has different limit. The browser IE and Safari limit to 2k, Opera 4k and Firefox 8k. means the max length for the GET request is 8k and min request length is 2k.

If exceed the request max length then the request truncated outside the limit by web server or browser without any warning. Some server truncated request data but the some server reject it because of data lose and they will return with response code 414.