netcdf-c

mirror/netcdf-c

Fork 0

mirror of https://github.com/Unidata/netcdf-c.git synced 2025-01-18 15:55:12 +08:00

Commit Graph

Author	SHA1	Message	Date
Dennis Heimbigner	c3c89693c4	Fix URL encoding in DAP2 url processing re: Github issue https://github.com/Unidata/netcdf-c/issues/1832 and Github issue https://github.com/Unidata/netcdf4-python/issues/1041 Handling of URL escape sequences for some servers (e.g. http://iridl.ldeo.columbia.edu) appears to be somewhat non-standard. In particular, certain characters need escaping that other servers do not. Fortunately, the changes should also work existing other servers.	2020-09-08 12:41:12 -06:00
Dennis Heimbigner	313121a229	Use proper CURLOPT values for VERIFYHOST and VERIFYPEER re: https://github.com/Unidata/netcdf-c/issues/1684 re: e-support VZL-904142 Two issues: 1. As of libcurl 7.66, the semantics of CURLOPT_SSL_VERIFYHOST changed so that the non-zero values affects certificate processing. 2. The current library was forcing the values of VERIFYPEER and VERIFYHOST to zero instead of leaving them to the default values. Solution was first to leave the defaults in place for VERIFYPEER and VERIFYHOST as long as they are not set in .ocrc/.dodsrc file. Second, the value of HTTP.SSL.VERIFYPEER or HTTP.SSL.VERIFYHOST as set in .ocrc/.dodrc is used to set the corresponding CURLOPT flags. So for example, adding > HTTP.SSL.VERIFYHOST=2 will set the value of CURLOPT_SSL_VERIFYHOST to 2, the default. Using > HTTP.SSL.VERIFYHOST=0 will set the value of CURLOPT_SSL_VERIFYHOST to 0, which disables it. Similarly for VERIFYPEER. Finally the semantics of HTTP.SSL.VALIDATE is now equivalent to > HTTP.SSL.VERIFYPEER=1 > HTTP.SSL.VERIFYHOST=2	2020-04-10 13:42:27 -06:00
Ward Fisher	2e63392423	Shuffling NUG and documentation.	2020-02-06 16:14:25 -07:00

Author

SHA1

Message

Date

Dennis Heimbigner

c3c89693c4

Fix URL encoding in DAP2 url processing

re: Github issue https://github.com/Unidata/netcdf-c/issues/1832
and Github issue https://github.com/Unidata/netcdf4-python/issues/1041

Handling of URL escape sequences for some servers
(e.g. http://iridl.ldeo.columbia.edu) appears to be somewhat
non-standard.
In particular, certain characters need escaping that other servers
do not. Fortunately, the changes should also work existing other servers.

2020-09-08 12:41:12 -06:00

Dennis Heimbigner

313121a229

Use proper CURLOPT values for VERIFYHOST and VERIFYPEER

re: https://github.com/Unidata/netcdf-c/issues/1684
re: e-support VZL-904142

Two issues:
1. As of libcurl 7.66, the semantics of CURLOPT_SSL_VERIFYHOST
   changed so that the non-zero values affects certificate processing.
2. The current library was forcing the values of VERIFYPEER
   and VERIFYHOST to zero instead of leaving them to the default values.

Solution was first to leave the defaults in place for VERIFYPEER and VERIFYHOST
as long as they are not set in .ocrc/.dodsrc file.
Second, the value of HTTP.SSL.VERIFYPEER or HTTP.SSL.VERIFYHOST
as set in .ocrc/.dodrc is used to set the corresponding CURLOPT flags.
So for example, adding
> HTTP.SSL.VERIFYHOST=2
will set the value of CURLOPT_SSL_VERIFYHOST to 2, the default.
Using
> HTTP.SSL.VERIFYHOST=0
will set the value of CURLOPT_SSL_VERIFYHOST to 0, which disables it.
Similarly for VERIFYPEER.

Finally the semantics of HTTP.SSL.VALIDATE is now equivalent to
> HTTP.SSL.VERIFYPEER=1
> HTTP.SSL.VERIFYHOST=2

2020-04-10 13:42:27 -06:00

Ward Fisher

2e63392423

Shuffling NUG and documentation.

2020-02-06 16:14:25 -07:00

3 Commits