Can't import CSV over HTTP due to incorrect HTTP Host header value about neo4j HOT 4 OPEN

hi @tomasherout, thanks for trying with HTTPS. Just to update you that we are still looking into this.

from neo4j.

Hi @tomasherout,

I can see that neo4j does substitute the resolved ip when using http to avoid an extra DNS lookup and minimise the possibility of DNS spoofing, but is the error below not related to the combination of using HTTP and Amz-SignedHeaders, Amz-Signature parameters? Have you tried using HTTPS?

<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><Key>test.csv</Key><BucketName>neo4j</BucketName><Resource>/test.csv</Resource><RequestId>17B444F268862189</RequestId><HostId>0cc3fecb-7862-44fa-aa60-e073c8a964ad</HostId></Error>

from neo4j.

Hello Phil,

error SignatureDoesNotMatch is the result of unexpected value of Host header (X-Amz-SignedHeaders=host in URI Search Params) because the value is different then what has been signed.

RFC 2616 (HTTP/1.1) https://datatracker.ietf.org/doc/html/rfc2616#section-14.23 says: The Host field value MUST represent
the naming authority of the origin server or gateway given by the original URL.

I can try HTTPS tomorrow and I will provide an update.

UPDATE: HTTPS works okay

from neo4j.

hi @tomasherout, thanks for your on-going patience. This could take some time as we are discussing internally how best to proceed in the most secure way. In the meanwhile, your options are to stick with HTTPS, or to use neo4j version <=5.15 if possible.

from neo4j.