Hexagon Geospatial
MENU

Developer Discussions

Discuss topics with other Hexagon Geospatial Power Portfolio developers and experts to get the most out of our products.
Showing results for 
Search instead for 
Do you mean 
Reply
Occasional Contributor
Posts: 18
Registered: ‎11-07-2016

Request Entity is Too Large

Hi

 

When running a WFS filter on a string of elements larger than say 75 items, I get error message "413 Request Entity Too Large".

 

 filters: [{
operator: "IN",
operands: ["{http://www.intergraph.com/geomedia/gml}PROCEDURE_ID", strProcedureIDs]
}],

 

 

Is there a workaround for this? A web.config setting or something?

 

Thanks

 

Brad

Technical Evangelist
Posts: 927
Registered: ‎09-11-2015

Re: Request Entity is Too Large

[ Edited ]

Hi Brad,

 

Yes:

1) Either use POST request. Geospatial Portal should use this approach by default, unless there's a forceHttpGet service quirk defined for WFS.

2) Or, follow the Additional Environment Configuration article - section Setting Query String Length for Long Requests.

 

Regards,

Jan

 

EDIT: Link fixed

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

Staff
Posts: 274
Registered: ‎02-04-2016

Re: Request Entity is Too Large

[ Edited ]

Hi Brad,

 

Assuming you are using WebMap/SDI WFS service, you could increase the default 64kb limit on the message size by changing the WFS web.config

 

FROM:

 

      <basicHttpBinding>

        <binding name="basicHttpBinding">

          <!-- If you wish to run the service over HTTPS transport change the mode from None to Transport -->

          <security mode="None">

            <transport clientCredentialType="None" />

          </security>

        </binding>

      </basicHttpBinding>

 

 

TO:

 

 

      <basicHttpBinding>

        <binding name="basicHttpBinding" maxReceivedMessageSize="10485760" maxBufferSize="10485760">

          <!-- If you wish to run the service over HTTPS transport change the mode from None to Transport -->

          <security mode="None">

            <transport clientCredentialType="None" />

          </security>

        </binding>

      </basicHttpBinding>

 

 

 

 

 

Hope this helps

 

Regards,

 

Frank

 

Occasional Contributor
Posts: 18
Registered: ‎11-07-2016

Re: Request Entity is Too Large

Hi

 

This didn't work:

<binding name="basicHttpBinding" maxReceivedMessageSize="10485760" maxBufferSize="10485760">

 

However, this did work:

<binding name="webHttpBinding" maxReceivedMessageSize="10485760" maxBufferSize="10485760">

 

Is it because the "post" endpoint is bound to webHttpBinding?

 

Thank you for puting me on the right track.

 

Occasional Contributor
Posts: 18
Registered: ‎11-07-2016

Re: Request Entity is Too Large

Hi

 

The hyperlink to Additional Environment Configuration is dead. Can you repost it?

 

Thanks

 

Occasional Contributor
Posts: 18
Registered: ‎11-07-2016

Re: Request Entity is Too Large

Spoke too soon. The 413 error is gone when using a slightly larger query, but now I get a "Service Returned an Exception" when running more than say 150 identifiers. I'm guessing the larger request is now being posted to the WFS service, but now it is the WFS service that can't process the request. Is there another configuration available?

 

Thanks

Staff
Posts: 274
Registered: ‎02-04-2016

Re: Request Entity is Too Large

Hi Brad,

 

What is the offending sample wfs request like (get the url from Developer tool on your browser, F12) ?

 

Thanks

 

Frank

Highlighted
hbm
Staff
Posts: 292
Registered: ‎11-05-2015

Re: Request Entity is Too Large

Be advised that depending on the data warehouse, there might be additional limitations on the complexity of a query. E.g. the Access MDB warehouse has a limitation on nesting of the where-clause and will fail with 32+ IDs.

Do you need immediate support?
Please submit a Ticket through our
Development Ticket Portal.