如何使用justhttp读取响应Cookie？获取AUTH Cookie值始终返回nil

Hey there! Let's troubleshoot why your AUTH cookie is returning nil when using JustHTTP. I've dealt with similar cookie-handling issues before, so let's walk through this step by step.

First, Verify the Request is Successful #

The most common reason for empty cookies is a failed request. If the server returns a 4xx/5xx status code, it might not send any cookies at all. Start by checking the basic request details:

let response = Just.get("https://url.com")
print("Status Code: \(response.statusCode)")
print("Request Succeeded? \(response.isSuccess)")
print("All Returned Cookies: \(response.cookies)")

Run this code first. If isSuccess is false or the status code isn't in the 200 range, you need to fix the request itself—check for typos in the URL, missing headers, or required authentication before this call.

Check if the AUTH Cookie Actually Exists #

Looking at the printed All Returned Cookies output, confirm there's a cookie named exactly AUTH (case matters!). Sometimes servers use lowercase auth or add prefixes like __AUTH, so double-check the exact name here.

Fix the Cookie Access Syntax #

Here's the likely culprit: JustHTTP's cookies property is an array of HTTPCookie objects, not a dictionary. Your original code tries to access it like cookies["AUTH"], which won't work for an array. Instead, filter the array to find the cookie by name:

let response = Just.get("https://url.com")

// Guard against failed requests
guard response.isSuccess else {
    print("Request failed: \(response.statusCode)")
    auth = nil
    return
}

// Find the AUTH cookie in the array
if let authCookie = response.cookies.first(where: { $0.name == "AUTH" }) {
    auth = authCookie.value
    print("Got AUTH cookie: \(auth!)")
} else {
    print("No AUTH cookie found in the response")
    auth = nil
}

Additional Checks if the Cookie Still Doesn't Show Up #

If you don't see the AUTH cookie in the printed list, consider these possibilities:

• You need to authenticate first: Some servers only send the AUTH cookie after a successful login request. Make sure you're sending a login POST request (with credentials) before calling this GET endpoint.
• Cookie domain/path restrictions: The cookie might be tied to a specific subdomain or path. Ensure your request URL matches the cookie's domain and path settings.
• HttpOnly flag: While HttpOnly prevents JavaScript from accessing the cookie, it doesn't block native code like yours from reading it, so this isn't the issue here.

内容的提问来源于stack exchange，提问作者Michael