[Geoserver-devel] [JIRA] (GEOS-8279) GWC direct integration gets fooled by non cacheable requests and returns tiles

[_Failed_to_Retrieve]

Andrea Aime created an issue

GeoServer / GEOS-8279

GWC direct integration gets fooled by non cacheable requests and returns tiles

Issue Type:	Bug
Assignee:	Unassigned
Components:	GWC
Created:	07/Sep/17 7:32 PM
Priority:	Medium
Reporter:	Andrea Aime

The two following requests: http://localhost:8080/geoserver/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&tiled=true&STYLES&LAYERS=importer%3ASENTINEL1-footprints&tilesOrigin=-180%2C-90&WIDTH=256&HEIGHT=256&SRS=EPSG%3A4326&BBOX=0%2C-180%2C180%2C0 http://localhost:8080/geoserver/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&tiled=true&STYLES&LAYERS=importer%3ASENTINEL1-footprints&tilesOrigin=-180%2C-90&WIDTH=256&HEIGHT=256&SRS=EPSG%3A4326&BBOX=0%2C0%2C180%2C180 Are clearly not cachable on the EPSG:4326 gridset and they span outside of the gridset bounds (the longitude goes down to -180 and up to 180) and yet GWC is not throwing any mis-alignment exception. This is happening because in GridSet.getClosestIndex does not use Math.abs, so if the difference between x and posX, y and posY is negative, the check does not trigger (in the -180 example, the difference on the y axis is -0.5)

Add Comment

Get JIRA notifications on your phone! Download the JIRA Cloud app for Android or iOS

This message was sent by Atlassian JIRA (v1000.1261.0#100059-sha1:3c555fd)