-
Notifications
You must be signed in to change notification settings - Fork 408
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
Fix #10701 enabling failures for wms requests with exception, for ImageWMS sources #10702
Conversation
…eption, for ImageWMS sources
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see my comment inline.
Just move the function in a proper file, and document it, for future improvements.
web/client/utils/VectorTileUtils.js
Outdated
@@ -13,3 +13,7 @@ export const VECTOR_FORMATS = [ | |||
]; | |||
|
|||
export const isVectorFormat = (format) => VECTOR_FORMATS.indexOf(format) !== -1; | |||
|
|||
export const isValidResponse = (response) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not a utility of vector tiles, but of WMS, so move this file.
Btw, even if I previously though that XML forma was enough, looking better, the WMS protocol tells to specify the format in the parameter.
https://docs.geoserver.org/main/en/user/services/wms/reference.html#exceptions
So let's document it a little, including what to improv. Something like "OGC protocol returns status = 200 with Exception in body, this function checks if the exception....".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please clean up vector tyle utils and move the test to WMSUtils tests
@ElenaGallo testable in DEV |
Description
Fix #10701 enabling failures for wms requests with exception, for ImageWMS sources
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#10701
What is the new behavior?
now it correctly triggers layerLoadError
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information