On 14-01-16 00:01, Robert Coup wrote: > HEAD /resource/path/to/directory > > Last-Modified: <timestamp> > > Content-Type: application/x-directory > > HEAD /resource/path/to/directory/file.png > > ETag: <md5 hash> > > Content-Length: 12345 > > Last-Modified: <timestamp> > > Content-Type: image/png > > Rob :)
Some comments on the HEAD proposal. * Last-modified is not a problem * Content-type: there is no way to determine the mime-type of a resource. There are ways for files, but there is nothing in the resourcestore API that makes it possible (other than attempting to derive it from the data itself.) But for directories, the HTTP header should specify the content-type of the content returned, which is XML, HTML or JSON, and not application/x-directory. * Content-length: there is no way to determine the size of a resource (except for reading through the whole thing and counting) So the way I see it, I am setting the datestamp in the header, so HEAD would be an alternative method to get last-modified info, but we'd still need the metadata operation to get the resource type. Regards Niels ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
