By the GeoWebCache documentation https://www.geowebcache.org/docs/current/services/tms.html the flipY parameter is what need.
The TMS specification has the TileGrid Map origin located at bottom left so Y coordinates grow up moving towards north. A vendor parameter “flipY=true” can be appended to the path to support Y coordinates numbered in the opposite ...
This is the default behavior, see also https://docs.geoserver.org/stable/en/user/geowebcache/index.html
It says: caching (storing) tiles as they are requested, eliminating redundant request processing and thus saving large amounts of processing time.
The file names of the cached tiles inside the GeoWebCache cache directories is not the usual z/y/x scheme. Tiles are spread along more directories (possibly in an effort to work nicer with the underlying filesystem).
The file naming algorithm has been already implemented in several places, for example in https://github.com/kcl-ddh/leaflet-geowebcache-plugin/...
The best way to do this is to have a single GWC that makes tile requests to each of the GeoServers in turn for tiles.
You can configure a Standalone GWC that points to a load balancer in front of the 8 GeoServers. GeoSolution's training documentation gives more details.
An alternative to that is to divide up your area of interest into 8 rectangles that ...
You need to set a Parameter filter, the easy way to do this is to go to the Tile Caching tab of the Layer page.
TIME is available in the Add Filter combo box and then you can choose to add either a fixed list of times to be cached or a regex that selects several times.
This is described in the GeoWebCache manual.
To work out what to put in a REST ...
If you want to use browser to view files on file system on your local machine, then for security reasons you cannot refer to those files by absolute path, you have to use relative path.
In your case that would mean that you have to put for example myTileViewer.html file with your code somewhere on the path to tiles, let's say in the folder C:/Program Files(...
The bounds of your request almost certainly don't align with the grid (138.2187, -33.1375) doesn't look like an even division of a lat/lon grid which I would expect to fall on numbers of degrees for a large number of zoom levels.
The simple solution is that if you want tiles then you should use a tiled map service like WMTS or TMS and take the guess work out ...
GeoWebCache has no idea that you've updated the index file or the mosaic, so you first need to delete the tiles that fall within the bounding box of the new imagery and then ask it to generate missing tiles.
The bbox and width and height in the WMS request should match exactly the boundaries of the tiles. In your first example you are close and in the second far away from correct values. You can turn the fullWMS mode on as documented in https://docs.geoserver.org/master/en/user/geowebcache/using.html and then GWC should send image for any GetMap be selecting, ...
To answer my own question, based on this Packet video at 5:27
When the contact is made to the GeoWebCache endpoint, GeoWebCache will
check on the file system to see if that image tile has already been
created, and if so that tile will be served back to the browser as a
response to the http request. If that tile is not already available,
The real answer is, you can't.
Because of this.
Geoserver uses an instance of custom Executor class, and this instance is created as Spring Bean in a geowebcache-core-context.xml file. When you download geoserver.war it's buried in a gs-gwc-<version>.jar inside WEB-INF\lib directory.
So the options are:
Submit a PR to GeoServer and GeoWebCache ...