| 123 | === GDAL_HTTP_VERSION === |
| 124 | |
| 125 | (GDAL >= 2.3) Can be set to 1.0, 1.1, 2 or 2TLS to specify which HTTP version to use. Will default to 1.1 generally (except on some controlled environments, like Google Compute Engine VMs, where 2TLS will be the default). Support for HTTP/2 requires curl 7.33 or later, built against nghttp2. "2TLS" means that HTTP/2 will be attempted for HTTPS connections only. Whereas "2" means that HTTP/2 will be attempted for HTTP or HTTPS. The interest of enabling HTTP/2 is the use of HTTP/2 multiplexing when reading GeoTIFFs stored on /vsicurl/ and related virtual file systems. |
| 126 | |
| 127 | === GDAL_HTTP_MULTIPLEX === |
| 128 | |
| 129 | (GDAL >= 2.3) Can be set to YES or NO. Defaults to YES. Only applies on a HTTP/2 connection. If set to YES, HTTP/2 multiplexing can be used to download multiple ranges in parallel, during ReadMultiRange() requests that can be emitted by the GeoTIFF driver. |
| 130 | |
| 131 | === GDAL_HTTP_MULTIRANGE === |
| 132 | |
| 133 | (GDAL >= 2.3) Can be set to SINGLE_GET, SERIAL or YES. Defaults to YES. Controls how ReadMultiRange() requests emitted by the GeoTIFF driver are satisfied. SINGLE_GET means that several ranges will be expressed in the Range header of a single GET requests, which is not supported by a majority of servers (including AWS S3 or Google GCS). SERIAL means that each range will be requested sequentially. YES means that each range will be requested in parallel, using HTTP/2 multiplexing or several HTTP connections. |
| 134 | |
| 135 | === GDAL_HTTP_MERGE_CONSECUTIVE_RANGES === |
| 136 | |
| 137 | (GDAL >= 2.3) Can be set to YES or NO. Defaults to NO. Only applies when GDAL_HTTP_MULTIRANGE=YES. Defines if ranges of a single ReadMultiRange() request that are consecutive should be merged into a single request. |
| 138 | |