The configuration files have been maintained with a deprecated comment in order to maintain your on disk cache of the data. Please note some WMS layer sources have been deprecated in v2.1.0. In addition to HTTPS endpoints specified by default, there are a number of improvements and bug fixes. To summarize, the best option, if available, is to update to v2.1.0. This class is a copy of the NASAWFSPlaceNamesLayer class but updates the hard coded service link to HTTPS. The patch jar includes a new PlaceNames layer: NASAWFSPlaceNamesLayerHttps.java. $ java .config.document=worldwind-2.0.0-https-patch/worldwind-https-patch.xml Place the jar in the classpath of your project and add the following argument to your application launch script. WorldWind Java v2.1.0 uses HTTPS map layers exclusively. SDK v2.1.0 and v2.0.0 are interface compatible.ĭownload the WorldWind Java v2.0.0 HTTPS Patch jar from GitHub. Option 1: Upgrade to WorldWind Java v2.1.0 (Preferred) SEVERE: Retrieval returned no content for You may see the following errors: FINE: Response code 301, Content length 534, Content type text/html charset=iso-8859-1, retrieving Clients map layer configuration files must be updated to use HTTPS endpoints. The Java URLConnection class does not follow the redirect protocol. HTTP requests return a redirect to the HTTPS endpoint. Problem: NASA Map Layers do not download (HTTP 301)Īs of January 2017 WorldWind map servers (worldwind*., .gov, and .gov) exclusively use HTTPS. Those problems and their fix are listed here. Many problems encountered by WorldWind developers and their application users have common causes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |