You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Mark Adamcin (Jira)" <ji...@apache.org> on 2021/08/27 15:16:00 UTC
[jira] [Commented] (OAK-9548) Azure Blob Store Presigned Url Param
"blockId" does not match official Azure REST API contract
[ https://issues.apache.org/jira/browse/OAK-9548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405871#comment-17405871 ]
Mark Adamcin commented on OAK-9548:
-----------------------------------
[~kwin] I think this patch would make Azurite useful to you for development for JCR-4705, JCR-4707, and JCRVLT-548.
> Azure Blob Store Presigned Url Param "blockId" does not match official Azure REST API contract
> -----------------------------------------------------------------------------------------------
>
> Key: OAK-9548
> URL: https://issues.apache.org/jira/browse/OAK-9548
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: blob-cloud-azure
> Affects Versions: 1.40.0
> Reporter: Mark Adamcin
> Priority: Minor
> Attachments: OAK-9548-blockId-to-blockid.patch, org.apache.jackrabbit.oak.plugins.blob.datastore.AzureDataStore.cfg.json
>
>
> I'm trying to get Direct Binary Upload to work locally using an Azurite blob service emulator. I've run into an issue where the {{blockId}} parameter for a PUT block request from an AEM Cloud SDK instance is failing to match the necessary operation in the Azure OpenAPI spec and Azurite is not tolerating the difference in casing when compared to the serialized form, {{blockid}}.
> Link: source of issue in [AzureBlobStoreBackend.java|https://github.com/apache/jackrabbit-oak/blob/c6ddcc55bee3de915459af01e91edad32d538f3d/oak-blob-cloud-azure/src/main/java/org/apache/jackrabbit/oak/blob/cloud/azure/blobstorage/AzureBlobStoreBackend.java#L972]
> Link: [Azure Put Block REST API|https://docs.microsoft.com/en-us/rest/api/storageservices/put-block#uri-parameters]
> I've confirmed that simply rewriting the oak-signed URL to change the only the one parameter name, i.e., by hacking the JS clientlib for the AEM Assets UI, fixes the issue with Azurite.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)