[MapProxy] HTTP status code for missing tiles

[dirk.thalheim at bkg.bund.de]

Hello Jukka,

thanks for the response. Too bad the WMTS standard is missing it. I see 500 is somehow the right choice.

Kind regards,

Dirk

Von: Rahkonen Jukka (MML) [mailto:jukka.rahkonen at maanmittauslaitos.fi]
Gesendet: Mittwoch, 29. August 2018 16:51
An: Thalheim, Dirk <dirk.thalheim at bkg.bund.de>; mapproxy at lists.osgeo.org
Betreff: Re: HTTP status code for missing tiles

Hi,

WMTS standard does not define 404 as an alternative. I would say that 500 is just right for your case.

Table 24 - HTTP exception codes and meanings on GetTile operation
exceptionCode value
HTTP Status Code
Code Message
OperationNotSupported 501 Not implemented
MissingParameterValue 400 Bad request
InvalidParameterValue 400 Bad request
TileOutOfRange 400 Bad request
NoApplicableCode 500 Internal server error


-Jukka Rahkonen-

Lähettäjä: MapProxy [mailto:mapproxy-bounces at lists.osgeo.org] Puolesta dirk.thalheim at bkg.bund.de<mailto:dirk.thalheim at bkg.bund.de>
Lähetetty: 29. elokuuta 2018 15:50
Vastaanottaja: mapproxy at lists.osgeo.org<mailto:mapproxy at lists.osgeo.org>
Aihe: [MapProxy] HTTP status code for missing tiles

Hello list,

we're providing a layer via WMTS which is based on a SQLite cache. The data is generated offline, so the cache in the mapproxy configuration has no source. In higher levels the cache contains only data for our area of interest (Germany + buffer). When I'm requesting the WMTS outside our area of interest, but inside the tile grids extend, I'm getting an Service-Exception like this one:
<ows:ExceptionReport xsi:schemaLocation="http://www.opengis.net/ows/1.1 http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd<http://www.opengis.net/ows/1.1%20http:/schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd>" version="1.0.0" xml:lang="en">
  <ows:Exception exceptionCode="NoApplicableCode">
      <ows:ExceptionText>invalid request (/wmts/1.0.0/web/default/GRID/13/17690/26750.png)</ows:ExceptionText>
  </ows:Exception>
</ows:ExceptionReport>

The HTTP-status is set to 500, which indicates an internal server error. However I don't see any error messages on the server side. So I'm wondering if this is an expected behavior. Shouldn't be the status code set to 404 - Not Found?

Kind regards,

Dirk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy/attachments/20180830/e525923d/attachment.html>