Updated to Version 2 but having issues with HTTP Headers about apikit

[ishkawa]

Hi jyounus,

First of all, you should include in the migration guide that HTTPHeaderFields has changed to headerFields.

I've just updated this. Thank you for reporting!

Now to my problem, after I updated my existing classes to use headerFields, it doesn't seem to be picking up my custom header. I'm doing something like this right now:

var headerFields: [String: String] {
    return [APIHeaders.BasicAuth.rawValue: constructBasicAuth()!]
}

Inside the constructBasicAuth function, I have some print() statements which are NOT printing in the console. I'm not sure why, but it seems like it's not using the headerFields property at all?

I confirmed RequestType uses headerFields using following example request type:

struct FooRequest: RequestType {
    typealias Response = Void

    var baseURL: NSURL {
        return NSURL(string: "https://example.com")!
    }

    var method: HTTPMethod {
        return .GET
    }

    var path: String {
        return "/"
    }

    var headerFields: [String : String] {
        return ["foo": "bar"]
    }

    func responseFromObject(object: AnyObject, URLResponse: NSHTTPURLResponse) throws -> Response {
        return ()
    }
}

test code:

let request = FooRequest()
let URLRequest = try! request.buildURLRequest()
print(URLRequest.allHTTPHeaderFields)
// Output: Optional(["Accept": "application/json", "foo": "bar"])

Could you confirm that your constructBasicAuth function executes print() correctly?

[jyounus]

It turns out, I was just being stupid.... There was a problem with my NodeJS backend that was causing an issue way before my actual request on the app side way being made.

Sorry and thanks for your help! I will open a PR with some fixed typos. :)