[Bug]: Body's specific headers overrides all the request/client set headers

[dariopellegrini]

Platform Version

iOS 16

SDK Version

1.7.2

Xcode Version

Xcode 14

Steps To Reproduce

I have this request

try await HTTPRequest {
            $0.path = "businesscards"
            $0.headers = HTTPHeaders([
                .authorization:"Bearer \(token)",
                .contentType:"multipart/form-data"
            ])
            
            $0.method = .post
            $0.body = try .multipart(boundary: nil, { form in
                if let name = businessCardCreation.name {
                    try form.add(string: name, name: "name")
                }
                if let surname = businessCardCreation.surname {
                    try form.add(string: surname, name: "surname")
                }
                if let email = businessCardCreation.email {
                    try form.add(string: email, name: "email")
                }
            })
        }.fetch().decode(BusinessCard.self, decoder: Decoders.decoder)

that is not sending Authorization header to the backend.

Expected Behavior

I expect to see the Authorization header in the backend.

Actual Incorrect Behavior

I can't see the authorization header in the backend.
Here is a screenshot of the headers sent in a local call, but the same happens on the cloud.

Trying the same request using Alamofire everything works.

[nashfive]

Have you tried to use the HTTPHeader.authBearerToken("") instead ?

[malcommac]

Hi @dariopellegrini , thank you for your report.

Unfortunately, @nashfive, It's a bug: due to a design choice, the headers property is just a forward to body.headers property, so when you assign the body to the request, it will override any previously set headers property.
We'll provide a fix ASAP.

Meanwhile, a possible workaround could be to set the $0.headers= after the body, and it should work fine.

[malcommac]

It will be merged in #63 with a minor release marked as 1.7.3.
An additional unit test was also added to mark and validate any further changes.
Thank you very much for your report.

[malcommac]

1.7.3 was published few minutes ago, and it's available both on SPM and CocoaPods.

[dariopellegrini]

@malcommac
I confirm that the bug is fixed in 1.7.3.

Thank you!