FI_22220: Staging portal using WMS 1.1.1 requests?

[nmtoken]

Originally posted as: https://forge.brgm.fr/issues/22220 Start date: | 22/01/2019 marked as resolved

James H. Passmore a écrit :

It appears the portal has reverted to using WMS version 1.1.1 requests instead of WMS 1.3.0 requests. I think we say now that a WMS version 1.3.0 only service is acceptable now, so this is a major issue.

We used to say that we had to support WMS 1.1.1 and WMS 1.3.0 because of issues with GeoNetwork in harvesting from WMS 1.3.0 services, but that restriction no longer applies.

Nicolas Mauroy a écrit :

What was done : We was looking for the service's version in the catalog the use this version. And 1.1.1 if the version was empty.

Just fixed : We changed this in the version available in staging to use 1.3.0 only. You are right, it was maybe a workaround for issues with geonetwork.

[nmtoken]

Issue has returned.

Staging portal (Portal v2020.0.1, which is same version as live) is making WMS 1.1.1 GetMap requests like:

https://onegeology.brgm-rec.fr/mapClient/proxyCesium.jsp?url=http%3A%2F%2Fservices.azgs.az.gov%2Farcgis%2Fservices%2FOneGeology%2FAZGS_Arizona_Geology%2FMapServer%2FWMSServer%3FSERVICE%3DWMS%26VERSION%3D1.1.1%26REQUEST%3DGetMap%26FORMAT%3Dimage%252Fpng%26TRANSPARENT%3Dtrue%26LAYERS%3DUS-AZ_AZGS_1M_Lithostratigraphy%26SRS%3DEPSG%253A4326%26STYLES%3D%26WIDTH%3D29%26HEIGHT%3D28%26BBOX%3D-115.35666127184022%252C30.888322150999013%252C-108.58347772732479%252C37.42794764225528&_=1603280604850

[nicolas-m-brgm]

Now forcing version 1.3.0 everytime. Available in staging

[nicolas-m-brgm]

We should not force 1.3.0 version. Portal should test if service is 1.3.0 compatible. If not, use 1.1.1 version.