I Think I found my answer:
However, our list of layers are dynamic (we are dynamically adding/removing layers via the REST Configuration API. So, is there a way to include those layers as part of GeoWebCache and enjoy its benefit? I won’t be able to predict the exact name/list of layers I will be seeing in my Geoserver at any given time.
Thanks,
Ronak Patel
From: Patel, Ronak Avinash (US SSA) [mailto:ronak.patel@anonymised.com]
Sent: Wednesday, May 12, 2010 6:23 PM
To: geoserver-users@lists.sourceforge.net
Cc: Wiyninger, Weldon R (US SSA); Froumis, James A (US SSA); Morgan, Michael L (GXP) (US SSA)
Subject: [Geoserver-users] GeoWebCache WMS Layers
Hello,
I’m forming Geowebcache urls and I’m getting back HTTP 400 errors back whenever I list more than one layer in the layers parameter.
So for example,
url will lead to a
00: Thread 74 Unknown layer everett:6da0e70c-5d6a-11df-a722-005056831642,everett:56885df8-5d69-11df-95e1-005056831642. Check the logfiles, it may not have loaded properly.
If I ask for layers, one at a time, the layers do exist and I get the proper output. I tried the above request without Geowebcache, and the expected output is correct.
Why would this occur with Geowebcache? Is this a known bug with Geoserver 2.0.1?
Thanks
Ronak Patel
Senior Software Engineer
BAE Systems NS
San Diego, CA