[Geoserver-users] GWC and workspace

Hello!

I’ve discovered strange behavior in GWC. If layer’s workspace is not provided in LAYERS param, the cache is not generated. Though tiles are coming on the client side. URLs to make it clear:

Tiles are coming, cache is not generated:
http://localhost:8080/geoserver/topp/gwc/service/wms?LAYERS=states&FORMAT=image/png&TILED=true&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&SRS=EPSG:3857&BBOX=-10331840.237812,4696291.0171875,-10018754.17,5009377.085&WIDTH=256&HEIGHT=256

Tiles are coming and cache is generated:
http://localhost:8080/geoserver/gwc/service/wms?LAYERS=topp:states&FORMAT=image/png&TILED=true&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&SRS=EPSG:3857&BBOX=-10331840.237812,4696291.0171875,-10018754.17,5009377.085&WIDTH=256&HEIGHT=256

So cache generation is depending on where workspace is specified. It is the second problem I ran into when workspace is in the address rather than in the param (the first problem was about styles).

GWC is not really aware of workspaces. It considers the whole prefixed name to be the name of the layer without any idea that it has two parts. There is presently no counterpart to GeoServer’s virtual services in GeoWebCache. So when using GWC you always have to give the full name of the layer.

···

On 18 February 2015 at 04:42, Sergey Kolosov <sergey.kolosof@anonymised.com> wrote:

Hello!

I’ve discovered strange behavior in GWC. If layer’s workspace is not provided in LAYERS param, the cache is not generated. Though tiles are coming on the client side. URLs to make it clear:

Tiles are coming, cache is not generated:
http://localhost:8080/geoserver/topp/gwc/service/wms?LAYERS=states&FORMAT=image/png&TILED=true&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&SRS=EPSG:3857&BBOX=-10331840.237812,4696291.0171875,-10018754.17,5009377.085&WIDTH=256&HEIGHT=256

Tiles are coming and cache is generated:
http://localhost:8080/geoserver/gwc/service/wms?LAYERS=topp:states&FORMAT=image/png&TILED=true&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&SRS=EPSG:3857&BBOX=-10331840.237812,4696291.0171875,-10018754.17,5009377.085&WIDTH=256&HEIGHT=256

So cache generation is depending on where workspace is specified. It is the second problem I ran into when workspace is in the address rather than in the param (the first problem was about styles).


Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk


Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

I thought if GWC can transfer the tile without workspace, it can put this tile in the cache too. But now I see the background. Thanks, Kevin!

···

2015-02-18 22:32 GMT+03:00 Kevin Smith <ksmith@anonymised.com>:

GWC is not really aware of workspaces. It considers the whole prefixed name to be the name of the layer without any idea that it has two parts. There is presently no counterpart to GeoServer’s virtual services in GeoWebCache. So when using GWC you always have to give the full name of the layer.

On 18 February 2015 at 04:42, Sergey Kolosov <sergey.kolosof@anonymised.com> wrote:

Hello!

I’ve discovered strange behavior in GWC. If layer’s workspace is not provided in LAYERS param, the cache is not generated. Though tiles are coming on the client side. URLs to make it clear:

Tiles are coming, cache is not generated:
http://localhost:8080/geoserver/topp/gwc/service/wms?LAYERS=states&FORMAT=image/png&TILED=true&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&SRS=EPSG:3857&BBOX=-10331840.237812,4696291.0171875,-10018754.17,5009377.085&WIDTH=256&HEIGHT=256

Tiles are coming and cache is generated:
http://localhost:8080/geoserver/gwc/service/wms?LAYERS=topp:states&FORMAT=image/png&TILED=true&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&SRS=EPSG:3857&BBOX=-10331840.237812,4696291.0171875,-10018754.17,5009377.085&WIDTH=256&HEIGHT=256

So cache generation is depending on where workspace is specified. It is the second problem I ran into when workspace is in the address rather than in the param (the first problem was about styles).


Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/