← Back to context

Comment by joshstrange

2 days ago

I'm not sure what the other option is here? Keep old defaults and hope users update?

I wouldn't be happy to find out they did it /just/ to break third-party S3 providers but it seems like it's an easy enough thing to turn it off right?

I'm just not sure how comfortable I am with the phrasing here (or maybe I'm reading too much into it).

3 comments

joshstrange

Reply
julik  1 day ago

The other option is not being overly strict with the data you receive from a client, especially when dealing with a protocol which is not a standard.

  • joshstrange  1 day ago

    I think the issue is that the client (the SDK) is complaining about a missing header it’s expecting to receive due to a new default in the client.

    My guess is the client has options you pass in, they added a new default (or changed one, I’m not clear on that), and the new default sends something up to the server (header/param/etc) asking for the server to send back the new checksum header, the server doesn’t respond with the header, the client errors out.