WebGIS Discussions

[Jacques]

Hi guys,

We are experiencing an error on portal sdk and not on the OEM portal.

Both have the same workspace and same data source etc.

So identical except for the fact that the one is the OEM and the other the sdk.

The problem on the sdk is that when one request attribute data from a geometry element on the portal sdk we get the error 

Maximum request length exceeded.

Both from double clicking on the geometry or using the info tool under the tools tab.

This started happening after some additional data has been added to the legend.

When we remove a wmps service the attribute data starts showing again.

Or we can leave the wmps service and just remove a few legend entries.

So it seems that the amount of legend entries is causing this behaviour.

Did modify the wb.config :

<httpRuntime executionTimeout="3600" requestValidationMode="2.0" maxUrlLength="65535" maxQueryStringLength="2097151" />

does not seem to remedy the issue.

Any help regarding the matter will be appreciated.

Kind Regards

Jacques

[lukasz.baraniak]

Have you also modified the <security> section of the web.config to match the OEM instance's web.config?

    <security>
      <requestFiltering>
        <requestLimits maxUrl="65535" maxQueryString="65535" maxAllowedContentLength="1073741824">
          <headerLimits>
            <add header="Content-type" sizeLimit="65535" />
          </headerLimits>
        </requestLimits>
      </requestFiltering>
    </security>

[Jacques]

Hi hbm,

No I have not.

I will make the changes as you suggest,and test and get back to you.

Kind Regards

Jacques

[Jacques]

Hi hbm,

Sorry for the delayed response.

I have checked the sdk web.config and saw that this changes has been implemented some time back (bad memory )

We have republished the staging(sdk) portal(also had this symptom) workspace etc and cleared all related cache , attribute data display now.

Will do this on the production portal (other sdk portal instance with this symptom) and re-test it and get back to you.

Kind Regards

Jacques

[Jacques]

Hi hbm,

Just for interest sake, regarding the security entry you mentioned.

This has been implemented on both SDK portal web.config's but not in the OEM's web.config.

I have also had a look in the OEM instance template web.config and it is also not present there.

Regardless , the OEM did not present this problem.

So something else caused it on the SDK side.But like I said in my previous post , the staging portal sdk is working now , will do the same for production and see if the issue is resolved.

Kind Regards

Jacques

[Jacques · Accepted solution]

Hi hbm,

It looks like the issue has been resolved.

Changed node entries <system.web> from:

<httpRuntime executionTimeout="3600" requestValidationMode="2.0" maxUrlLength="65535" maxQueryStringLength="2097151" />

to:

<httpRuntime maxRequestLength="1048576" />

Changed node enttry <system.webserver> from :

<security>
<requestFiltering>
<requestLimits maxUrl="65535" maxQueryString="65535" maxAllowedContentLength="1073741824">
<headerLimits>
<add header="Content-type" sizeLimit="65535" />
</headerLimits>
</requestLimits>
</requestFiltering>
</security>

To:

   <security>
      <requestFiltering>
         <requestLimits maxAllowedContentLength="1073741824" />
      </requestFiltering>
   </security>

Only made these changes on the one machine , same sdk version on all 3 , 2 work with no changes , 1 did not.