Hi! I'm working with http4-connect (which is reall...
# http4k
Hi! I'm working with http4-connect (which is really great btw) and I'm facing an issue. In our organization, there is an on-premise S3 installation on an internal domain. I noticed that http4k-aws and http4k-connect have
domain hardcoded. When I change the domain with
, the signature process seems to fail: I get an AccessDenied response, even if the request is correct. By trying the same request with Postman and its included AWS Signature feature, I got a different
: • Postman:
• Http4k-connect:
So I think there are those two possibilities, either the signature is wrong due to a late host change, or the signature needs to sign
too. Either way, it would be nice to be able to set the base domain.
aha - that's going to be an interesting one - I literally didn't even know you could get custom S3 installs! For the moment, could you simply write a custom the S3 adapter to suit your situation using the same actions? It's only a few lines of code. and you will be able to use all the same actions as we do in the original
can you raise an issue to remind me to look at it in the meantime?
the problem is that the host change is too late, so the original host is the one used in the signed headers
the content hash is unaffected
Alright, I'm going to raise an issue about it. Thank you for your swift response 🙂 I'll try to make it work as you say