maxQueryStringLength error when clicking the print button

Stimulsoft Reports.WEB discussion
Post Reply
eric_stimulsoft
Posts: 25
Joined: Tue Feb 25, 2014 5:14 am
Location: Jupiter

maxQueryStringLength error when clicking the print button

Post by eric_stimulsoft »

Hi,

I'm using the web StiMvcViewer and i am encountering a NetworkError: 400 Bad Request whenever im pressing the print button.

Here is the exact error message:
The length of the query string for this request exceeds the configured maxQueryStringLength value.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Upon checking the GET request that failed, i saw that the data that was use from a previous ajax POST (the contents of the data is an object with several array properties) was used as a parameter under the name of formValues.

What i would like to know is why did it used the previous data of my POST request as formValues and is there a way to prevent this?
I'm using the 2014.2.1912 pre release build.

Hoping for your fast reply.

Thanks!
Vladimir
Posts: 1462
Joined: Fri Apr 13, 2007 4:05 am
Location: Earth

Re: maxQueryStringLength error when clicking the print butto

Post by Vladimir »

Hello,

Sorry, we need a little more tive for answer.

Thank you.
eric_stimulsoft
Posts: 25
Joined: Tue Feb 25, 2014 5:14 am
Location: Jupiter

Re: maxQueryStringLength error when clicking the print butto

Post by eric_stimulsoft »

Hello Vladimir,

Thank you for the reply, we will patiently wait for your answers.

Thanks!
Vladimir
Posts: 1462
Joined: Fri Apr 13, 2007 4:05 am
Location: Earth

Re: maxQueryStringLength error when clicking the print butto

Post by Vladimir »

Hello,

Sorry for delay in response.

The FormValues object is used to pass the form values to MvcViewer actions in order to use these values when loading/building/exporting/printing the report. Values are stored in the case, if the viewer page was initialized by POST request with the form values.

To prevent this behavior you can, for example, use an intermediate page for processing parameters. Also, we can add an option for the viewer, which will disable the transmission of form values.

Thank you.
eric_stimulsoft
Posts: 25
Joined: Tue Feb 25, 2014 5:14 am
Location: Jupiter

Re: maxQueryStringLength error when clicking the print butto

Post by eric_stimulsoft »

Hi Vladimir,

Thank you for the explanation, may i know when will that option for the viewer be available?

Thanks!
Vladimir
Posts: 1462
Joined: Fri Apr 13, 2007 4:05 am
Location: Earth

Re: maxQueryStringLength error when clicking the print butto

Post by Vladimir »

Hello,

We will try to add the new option to the next prerelease build.

Thank you.
Post Reply