mirror of
https://github.com/HDFGroup/hdf5.git
synced 2026-09-25 04:09:44 +03:00
Aleksandar Jelenak
55d179733c
The ROS3 VFD appended the raw object key to the HTTP request path. Because the signing configuration disables use_double_uri_encode (the correct setting for S3), the SigV4 signer uses the request path verbatim, so keys containing characters that AWS requires to be percent-encoded -- such as '=' in Hive-style "key=value" partition prefixes, '+', or spaces -- produced signatures that disagree with S3's server-side recomputation. S3 rejects such requests with SignatureDoesNotMatch, surfaced as a bodyless HTTP 403 that is indistinguishable from a permissions error on a HEAD request, even though other S3 clients (AWS CLI, boto3, s3fs) could read the same objects.
The config directory
Intro
HDF5 can be configured using CMake.
Configuration information for the HDF5 library and tools is
specific to the repository folders. Each subdirectory of the project
has its own CMake build and test files. Basic library configuration will generally
be found in the root's CMakeLists.txt with support for macros and settings
in this config directory.
This directory contains a few important things:
- Support files for optional components (in
cmake) - Compiler and platform parameters (in
flags) - Warning files (in
*-warningsdirectories) - Toolchain files (in
toolchain) - Sanitizer files (in
sanitizer) - Example install scripts (in
examples) - Installation support files (in
install)
CMake is documented in the following files in the docs/ directory: