WFS 1.1.0 ExceptionReport response handling : QGIS looks for 'exceptionCode' but in specifications it's 'code' attribute

[Yolecomte]

When using a WFS service that implements the version 1.1.0, if an exception occured the specs tells to return an xml which might looks like this (chapter 7.7):

<?xml version="1.0" ?> 
<ExceptionReport    version="1.1.0"    xmlns="http://www.opengis.net/ogc"    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"    xsi:schemaLocation="owsExceptionReport.xsd">  
      <Exception code="999" locator="INSERT STMT 01">       
            <ExceptionText>parse error: missing closing tag for element wkbGeom</ExceptionText>    
      </Exception> 
</ExceptionReport>

We can see that the <Exception> tag can include a code attribute.

When QGIS receive such a response from WFS service after something went wrong, it seems that it looks for an exceptionCode attribute.

here in current master :

QGIS/src/providers/wfs/qgswfsprovider.cpp

Line 1980 in df4d03d

.arg( exception.attribute( QStringLiteral( "exceptionCode" ), tr( "missing" ) ),

)

Not sure if there is a problem in QGIS or if I misunderstand the mentionned part of code but with that behavior we always get a missing code in client gui error dialog .

[elpaso]

@Yolecomte looks like an easy fix, it's probably enough to check for the code in case of version 1.1

[Yolecomte]

@elpaso Thank's for quick answer.

Actually, even in version 1.0.0 it seems that we can send a code attribute from the specs. The difference is in 1.0.0 the first tag is <ServiceExceptionReport> and we fall back here in QGIS code (no attribute are checked and you only get the text message):

QGIS/src/providers/wfs/qgswfsprovider.cpp

Line 1956 in df4d03d

if ( exceptionElem.tagName() == QLatin1String( "ServiceExceptionReport" ) )

Anyhow, nothing critical here!