[mapguide-users] WFS Select Within MGOS 3.1.2

Gordon Luckett gordon.luckett at arrowgeomatics.com
Tue May 17 12:53:25 PDT 2022


Thanks Jackie,
Yes, both the WFS (MapGuide) server's IIS is set to max sizes for Request
parameters and POST/GET requests.

The Select Within in Fusion calls:
GetParent().Fusion.xml2json(callback, r);

which causes the error
*Exception: An exception occurred in FDO component. Error occurred in
Feature Source (Library://WFS/SANDBOX_WFS.FeatureSource): Unexpected error
encountered while accessing the server. (Cause: The requested URL returned
error: '413 Request entity too large: request URL path too large'. , Root
Cause: The requested URL returned error: '413 Request entity too large:
request URL path too large'. ) -
MgRenderingServiceHandler.ProcessOperation() line 83 file
c:\working\build_area\mapguide\3.1.2\x64\mgdev\server\src\services\rendering\RenderingServiceHandler.cpp
- MgOpQueryFeatures.Execute() line 125 file
c:\working\build_area\mapguide\3.1.2\x64\mgdev\server\src\services\rendering\OpQueryFeatures.cpp
- MgServerRenderingService.QueryFeatures() line 1093 file
c:\working\build_area\mapguide\3.1.2\x64\mgdev\server\src\services\rendering\ServerRenderingService.cpp
- MgServerRenderingService.RenderForSelection() line 1823 file
c:\working\build_area\mapguide\3.1.2\x64\mgdev\server\src\services\rendering\ServerRenderingService.cpp
- MgServerFeatureService.SelectFeatures() line 451 file
c:\working\build_area\mapguide\3.1.2\x64\mgdev\server\src\services\feature\ServerFeatureService.cpp
- MgServerSelectFeatures.SelectFeatures() line 331 file
c:\working\build_area\mapguide\3.1.2\x64\mgdev\server\src\services\feature\ServerSelectFeatures.cpp*




On Wed, May 11, 2022 at 8:31 AM Jackie Ng <jumpinjackie at gmail.com> wrote:

> Hi Gordon,
>
> A 413 error is most likely being thrown at the IIS/Apache web server
> level. I know IIS has things like 30MB payload limits for POST requests.
> There's probably a similar restriction on URL length.
>
> Failing that, try using POST instead of GET for the WFS select within if
> it's possible as for POST all request parameters will be in the submitted
> body and not specified in the URL.
>
> - Jackie
>
> You wrote:
>
> Hi All,
>
> has anyone had any success with "select-within" selecting WFS generated
>
> layers?
>
> Currently getting a '413 Request entity too large: request URL path too
>
> large' with only my layers coming from WFS.
>
> Trying to figure out if it's a bug or my setup.
>
> thanks
>
> gordon
>
>
>
> --
> *Please Note: I no longer create new posts or post replies to any OSGeo
> mailing list through nabble. As a result, you most likely won't see this
> message appear on nabble's view of any OSGeo mailing list and may only see
> this message through mailing list archives or depending on your mailing
> list subscription settings, through daily message digests or automated
> notifications from the mailing lists.*
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapguide-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20220517/528889d9/attachment.htm>


More information about the mapguide-users mailing list