<la:link href="../uploadpage/${f:u(dictId)}"
                                                 styleClass="btn btn-success btn-xs">
                                            <i class="fa fa-upload" aria-hidden="true"></i>
                                            <la:message key="labels.dict_kuromoji_link_upload"/>
                                        </la:link>
                                    </div>

                                        <la:link href="../uploadpage"
                                                 styleClass="btn btn-success btn-xs">
                                            <i class="fa fa-upload" aria-hidden="true"></i>
                                            <la:message key="labels.elevate_word_link_upload"/>
                                        </la:link>
                                    </div>

	// does not match the secret key used during encrypting the object.
	ErrSecretKeyMismatch = Errorf("The secret key does not match the secret key used during upload")

	// ErrCustomerKeyMD5Mismatch indicates that the SSE-C key MD5 does not match the
	// computed MD5 sum. This means that the client provided either the wrong key for

                                    <la:link href="uploadpage/${f:u(dictId)}"
                                             styleClass="btn btn-success btn-xs ${f:h(editableClass)}">
                                        <i class="fa fa-upload" aria-hidden="true"></i>
                                        <la:message key="labels.dict_synonym_link_upload"/>
                                    </la:link>
                                </div>

            s3Client.putObject(request, RequestBody.fromInputStream(inputStream, size));
        } catch (final Exception e) {
            throw new StorageException("Failed to upload " + objectName, e);
        }
    }

    @Override
    public void downloadObject(final String objectName, final OutputStream outputStream) {
        try {

// - List of Smart Object Storage protocol capabilities supported by the server.
// Currently, there are three capabilities supported:
//   - Capacity Reporting
//   - Backup data locality for upload sessions (Veeam Smart Entity)
//   - Handover of IAM & STS Endpoints instead of manual definition in Veeam Backup & Replication. This allows Veeam
//     Agents to directly backup to object storage.
//

above. For example if the zone is `public`, use ```sh firewall-cmd --zone=public --add-port=9000/tcp --permanent ``` Note that `permanent` makes sure the rules are persistent across firewall start, restart or reload. Finally reload the firewall for changes to take effect. ```sh firewall-cmd --reload ``` ### iptables For hosts with iptables enabled (RHEL, CentOS, etc), you can use `iptables` command to enable all traffic coming to specific ports. Use below command to allow access to port 9000 ```sh iptables...

}

// ListMultipartUploadsHandler - GET Bucket (List Multipart uploads)
// -------------------------
// This operation lists in-progress multipart uploads. An in-progress
// multipart upload is a multipart upload that has been initiated,
// using the Initiate Multipart Upload request, but has not yet been
// completed or aborted. This operation returns at most 1,000 multipart
// uploads in the response.

Esto no es una limitación de **FastAPI**, es parte del protocolo HTTP.

///

## Subida de Archivos Opcional { #optional-file-upload }

Puedes hacer un archivo opcional utilizando anotaciones de tipos estándar y estableciendo un valor por defecto de `None`:

{* ../../docs_src/request_files/tutorial001_02_an_py310.py hl[9,17] *}

            storage.createFrom(blobInfo, inputStream);
        } catch (final Exception e) {
            throw new StorageException("Failed to upload " + objectName, e);
        }
    }

    @Override
    public void downloadObject(final String objectName, final OutputStream outputStream) {
        try {