[MapProxy] WMTS: ows:ExceptionReport reveales too much information

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[MapProxy] WMTS: ows:ExceptionReport reveales too much information

Tobias Wendorff
Hi there,

is there a way to restrict the information WMTS gives upon an exception?
Right now, the ows:ExceptionReport releaves pretty much system internas:

<ows:ExceptionText>
Postgis Plugin: ERROR: no such database: xxxxx Connection string:
'host=x.x.x.x port=xxxxx dbname=xxxxx user=xxxxx connect_timeout=x'
encountered during parsing of layer 'xxxxx' in Layer at line xxxxx of
'/xxxxx/xxxxx/xxxxx.xxxxx'
</ows:ExceptionText>

I've blanked out the data with an "x".

The Mapnik PostGIS plugin seems to generate this error, but from my
point of view, the normal user should not see this. It's fine for the
internal error log.

Can I just edit files like templates/wmts100exception.xml or will this
create new exceptions when parsing the templates?

Best regards,
Tobias

_______________________________________________
MapProxy mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapproxy