[
https://issues.apache.org/jira/browse/NIFI-14278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Turcsanyi updated NIFI-14278:
-----------------------------------
Description:
NIFI-11439 introduced Storage API URL property for GSC processors but
PutGCSObject is not working with custom endpoints.
For some reason, the Host header in the request was set to the default
[www.googleapis.com|http://www.googleapis.com/] which was inconsistent with the
custom (non-default) endpoint. It seems older GCS client library versions did
not take care of it but newer versions use the default public endpoint in this
case. Also, the library is able to automatically set the Host header based in
the endpoint URL, so explicit setting is not needed.
was:
NIFI-11439 introduced Storage API URL property for GSC processors but
PutGCSObject is not working with custom endpoints.
For some reason, the Host header in the request was set to the default
[www.googleapis.com|http://www.googleapis.com/] which was inconsistent with the
custom (non-default) endpoint. It seems older GCS client library versions did
not take care of it but it is causing error in newer versions. Also, the
library is able to automatically set the Host header based in the endpoint URL,
so explicit setting is not needed.
> Fix custom Storage API URL in PutGCSObject
> ------------------------------------------
>
> Key: NIFI-14278
> URL: https://issues.apache.org/jira/browse/NIFI-14278
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Peter Turcsanyi
> Assignee: Peter Turcsanyi
> Priority: Major
>
> NIFI-11439 introduced Storage API URL property for GSC processors but
> PutGCSObject is not working with custom endpoints.
> For some reason, the Host header in the request was set to the default
> [www.googleapis.com|http://www.googleapis.com/] which was inconsistent with
> the custom (non-default) endpoint. It seems older GCS client library versions
> did not take care of it but newer versions use the default public endpoint in
> this case. Also, the library is able to automatically set the Host header
> based in the endpoint URL, so explicit setting is not needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
