aws headers

Author: ehsan6sha

crates/fula-cli/src/routes.rs

@@ -260,8 +260,14 @@ fn create_cors_layer(origins: &[String]) -> CorsLayer {
         header::HeaderName::from_static("x-amz-content-sha256"),
         header::HeaderName::from_static("x-amz-date"),
         header::HeaderName::from_static("x-amz-copy-source"),
+        // Direct pinning headers
         header::HeaderName::from_static("x-pinning-service"),
         header::HeaderName::from_static("x-pinning-token"),
+        header::HeaderName::from_static("x-pinning-name"),
+        // S3-compatible x-amz-meta-* pinning headers (for MinIO and other S3 clients)
+        header::HeaderName::from_static("x-amz-meta-x-pinning-service"),
+        header::HeaderName::from_static("x-amz-meta-x-pinning-token"),
+        header::HeaderName::from_static("x-amz-meta-x-pinning-name"),
     ];
 
     let cors = CorsLayer::new()

docs/openAPI.yaml

@@ -400,6 +400,9 @@ paths:
             - Pinata: https://api.pinata.cloud/psa
             - Web3.Storage: https://api.web3.storage
             - NFT.Storage: https://nft.storage/api
+            
+            **S3 Client Compatibility**: Also accepts `x-amz-meta-x-pinning-service`
+            for S3 client libraries like MinIO that prefix custom headers.
           schema:
             type: string
             format: uri
@@ -409,6 +412,8 @@ paths:
           description: |
             User's IPFS Pinning Service access token (Bearer token).
             This is the user's own credential - NOT stored by the gateway.
+            
+            **S3 Client Compatibility**: Also accepts `x-amz-meta-x-pinning-token`.
           schema:
             type: string
         - name: x-pinning-name