[ https://issues.apache.org/jira/browse/JCLOUDS-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philipp Nanz updated JCLOUDS-1537: ---------------------------------- Summary: [BlobStore] Please clarify how to use GetOptions.Builder.ifETagDoesntMatch(String eTag) (was: [BlobStore] Explain how to use GetOptions.Builder.ifETagDoesntMatch(String eTag)) > [BlobStore] Please clarify how to use > GetOptions.Builder.ifETagDoesntMatch(String eTag) > --------------------------------------------------------------------------------------- > > Key: JCLOUDS-1537 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1537 > Project: jclouds > Issue Type: Wish > Reporter: Philipp Nanz > Priority: Major > > I have been fiddling around with the Azureblob provider in Jclouds in > conjunction with ETags. > I'm having a hard time trying to understand how this feature is intended to > be be used. My observation is that it fails with a generic > {{HttpResponseException}} with status code 304 in case the content was not > modified. Of course I can handle that in my calling code, it just feels a bit > weird. Even more weird seems to be the fact that I am receiving errors on the > log file in this case: > {quote} > 2020-01-14 15:27:34.091 ERROR 1872 --- [nio-8080-exec-7] > o.j.h.handlers.RedirectionRetryHandler : Cannot retry after redirect, no > host header: [method=org.jclouds.azureblob.AzureBlobClient.public abstract > org.jclouds.azureblob.domain.AzureBlob > org.jclouds.azureblob.AzureBlobClient.getBlob(java.lang.String,java.lang.String,org.jclouds.http.options.GetOptions[])[jobmanager-workspace, > 61044005-5ca7-4bbd-ab20-3a13897b6fc6\test\grumpy-cat.jpg, > [Lorg.jclouds.http.options.GetOptions;@65f6e083], request=GET > https://yaddayadda.blob.core.windows.net/jobmanager-workspace/61044005-5ca7-4bbd-ab20-3a13897b6fc6%5Ctest%5Cgrumpy-cat.jpg > HTTP/1.1] > [Fatal Error] :1:1: Vorzeitiges Dateiende. > {quote} > So apparently it would like to retry the request, which clearly makes no > sense. > Am I doing something wrong, or is this some kind of bug in the Azure provider > implementation? > Thanks for your time! -- This message was sent by Atlassian Jira (v8.3.4#803005)