Hi,
I used to be able to simply setup a data store for a shapefile using a public
facing AWS S3 URL for the Connection Parameters field and I could publish
layers/services for it with no problem. That was version 2.16.0 of Geoserver
(build date 18-Sep-2019).
However, on recent Geoserver deploys, the server mangles the URL and attempts
to turn it into a file URL like this one for example:
file:///usr/local/tomcat/webapps/Geoserver/https:/myshapefiles.s3.amazonaws.com/testshapefile1.shp
Which, prevents successful Publishing.
Is there a configuration or build option that allows this to work with a
standard web URL to the shapefile vs only allowing local files?
Thanks,Jonathan
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
