Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GetFeatureInfo format list in GetCapabilities not respected #302

Open
landryb opened this issue Dec 3, 2020 · 1 comment
Open

GetFeatureInfo format list in GetCapabilities not respected #302

landryb opened this issue Dec 3, 2020 · 1 comment

Comments

@landryb
Copy link
Member

landryb commented Dec 3, 2020

Same issue as #301 for GetFeatureInfo, whatever the formats proposed by the server mapstore assumes text/html and application/json are available.

by default mapserver has:

<GetFeatureInfo>
<Format>text/plain</Format>
<Format>application/vnd.ogc.gml</Format>

sure, i can add formats to that list by properly configuring mapserver, but only the formats supported by the server should be listed in the featureinfo layer dialog. Sure, its probably the default that's supported by geoserver, but still some interoperability tests would be nice..

@landryb
Copy link
Member Author

landryb commented Jan 27, 2023

for this issue, the goal is to prevent MS2 to do a GFI query on a server that doesnt support what MS2 expects (eg application/json or text/html depending on the formats) or only lists to the end-user the available formats.

I'm able to crash (Oops, something has gone wrong..) ms2 by selecting text/plain format for GFI on a mapproxy server which doesn't support this format (and replies with json)

on the same layer, using text/html for INFO_FORMAT parameter gets json,and ms2 bails out with There is no information available for this point but at least doesnt crash. A nicer error message would be much better for the end-user...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants