Hi Dave,
the callback in question extends the official OGC conditional capabilties
request (based on the
update sequence number) to non compliant clients that can do HTTP
conditional requests instead.
So the answer would be, "if something changes, you'd have to increment the
update sequence,
since your caps document changed".

However, I understand and agree this is indeed a problem, the capabilities
document can change
due to dimensions, but also due to security, without anything touching the
GeoServer configuration (which
would bump the update sequence).

As a quick fix, there is already a CAPABILITIES_CACHE_CONTROL_ENABLED
envvar/sysvar/servlet context variable
that can be set to false to disable the callback.

As a longer term fix, the callback should probably be modified to identify
elements making the caps
dynamic. Like, for example, scan the layers available to the current user
and create a digest out of them
(fixes security) and if during the scan any has dimensions, uh, probably
disable the conditional request fully.

On the background, there is still the issue of proper OGC clients making
update sequence based conditional
request, those will still fail to notice something has changed... this
mapserver ticket has enough information
about it without you needing to read the OWS specifications:
https://trac.osgeo.org/mapserver/ticket/2384

Hum... from what I read, the "etag" computed above could also be used for
conditional negotiation at the OGC
level.

Cheers
Andrea


On Fri, Mar 31, 2017 at 8:06 PM, Dave Blasby <[email protected]>
wrote:

> Hi,
>
> I noticed that the GetCap document was not up-to-date.  When I dug into
> it, I found that CapabilitiesCacheHeadersCallback was returning a 304
> (i.e. no changes).
>
> However, this is a timeseries dataset (ie. Time Dimension tab on Layer
> Publish).
>
> (i.e. a GeoGIG or PostGIS dataset with a time column)
>
> The issue is that the dataset is changing.  A new Time value is inserted
> into the dataset - the getcap (set to LIST) should show this new value.
> However, the document is cached because the catalog hasn't detected any
> changes.
>
> We talked about this earlier ("Time dimension on Vector Layer is SLOW")
> and decided that caching this information is inappropriate (and I agree)
> for this reason.
>
> What should be done about this?
>
> Thanks,
> Dave
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>


-- 
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to