Based on directives from the US Department of Homeland Security, we are required to transition our public-facing web services to use the HTTPS protocol and deprecate support for HTTP.  

All of our production web services currently support both HTTP and HTTPS, though beginning on March 13, 2017, any HTTP requests will return a “301 Moved Permanently” response code which most browsers will automatically redirect to use HTTPS.  Hopefully this transition will be seamless to most of you - please see here if any action is needed on your part:


Tool / LibraryImpact
Worldview usersUnaffected as it already uses HTTPS to retrieve GIBS imagery
OpenLayers / Leaflet / Cesium mapping librariesWill automatically redirect GIBS requests to HTTPS although this may incur extra network traffic during initial HTTP exchanges
Script-based access using GDALWill automatically redirect GIBS requests to HTTPS although this may incur extra network traffic during initial HTTP exchanges
Your custom mapping appUnknown!  Please see below for ways to test and upgrade

 

For most developers, this update should involve simply changing the GIBS service endpoint from http to https.  Here is a sample of previous endpoints for HTTP-based “geographic” tile requests:

http://map1.vis.earthdata.nasa.gov/wmts-geo/  (circa 2011-2016)

http://gibs.earthdata.nasa.gov/wmts/epsg4326/best/  (2016+)

 

These URLs should now be replaced by their HTTPS equivalent, e.g:

https://gibs.earthdata.nasa.gov/wmts/epsg4326/best/  (2016+)

 

See here for our full API documentation:

https://wiki.earthdata.nasa.gov/display/GIBS/GIBS+API+for+Developers

 

If you would like to test how your HTTP-based application will respond to the HTTP 301 redirect before the transition on March 13, 2017, you can use our User Acceptance Testing (UAT) environment which already has the redirect in place:

http://uat.gibs.earthdata.nasa.gov/wmts/epsg4326/best/

 

Please contact us at support@earthdata.nasa.gov if you have any questions or concerns.

  • No labels