Android中HttpURLConnectionImpl.getInputStream调用失败（403错误）

Alright, let's tackle this 403 Forbidden issue you're facing. The key clue here is that the URL works fine in a browser but fails with HttpURLConnection—this almost always boils down to missing or incorrect request headers that browsers automatically send, which the server expects.

First, Understand the Root Cause #

A 403 response means the server is rejecting your request. Since the browser succeeds, the difference lies in the HTTP headers each client sends. Browsers include headers like User-Agent, Accept, and Accept-Language by default, but HttpURLConnection uses minimal default headers, which might trigger the server's anti-bot or validation checks.

Step-by-Step Troubleshooting #

• Compare Request Headers: Use a tool like Charles Proxy or Fiddler to capture the HTTP request your browser sends to the Flickr API. Note all the headers (especially User-Agent). Then check what headers your HttpURLConnection is sending—by default, it's probably only sending a basic Dalvik/2.1.0-style User-Agent which might be blocked.
• Validate API Key: Even though the browser works, double-check that your API key is correctly spelled in your code. Typos happen, and sometimes browsers might cache a valid request while your code uses an invalid one.
• Check Request Method: Ensure you're using the same HTTP method as the browser (Flickr's getRecent uses GET, which is the default for HttpURLConnection, but it's worth confirming you haven't accidentally set it to POST).

Fixes to Implement #

1. Add Browser-like Request Headers

Update your HttpURLConnection setup to include headers that match what the browser sends. The User-Agent is usually the most critical one—many APIs block requests that don't look like they're coming from a legitimate browser. Example:

// Add these lines before calling connection.connect()
connection.setRequestProperty("User-Agent", "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36");
connection.setRequestProperty("Accept", "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8");
connection.setRequestProperty("Accept-Language", "en-US,en;q=0.5");

2. Fix Your Code Logic

Right now, you're calling getInputStream() before checking the response code. When the server returns 403, getInputStream() throws a FileNotFoundException (which you see in your logs). You should first check the response code, then decide whether to read the input stream or the error stream:

try {
    // First get the response code to avoid exceptions
    int responseCode = connection.getResponseCode();
    
    if (responseCode != HttpURLConnection.HTTP_OK) {
        Log.e("TAG", "Flickr API rejected request with code: " + responseCode);
        // Optional: Read error stream to get server's rejection message
        InputStream errorStream = connection.getErrorStream();
        if (errorStream != null) {
            BufferedReader reader = new BufferedReader(new InputStreamReader(errorStream));
            String line;
            StringBuilder errorMsg = new StringBuilder();
            while ((line = reader.readLine()) != null) {
                errorMsg.append(line);
            }
            Log.e("TAG", "Server error message: " + errorMsg.toString());
            reader.close();
        }
        return null;
    }

    // If response is OK, proceed to read the input stream
    ByteArrayOutputStream out = new ByteArrayOutputStream();
    InputStream in = connection.getInputStream();
    int bytesRead = 0;
    byte[] buffer = new byte[1024];
    while ((bytesRead = in.read(buffer)) > 0) {
        out.write(buffer, 0, bytesRead);
    }
    in.close();
    out.close();
    
    return out.toByteArray();
} finally {
    Log.i("TAG", "Connection response code: " + connection.getResponseCode());
    connection.disconnect();
}

This way, you avoid the FileNotFoundException and can also get more details from the server about why the request was rejected.

Final Notes #

Flickr's API might have rate limits or specific header requirements, so mimicking the browser's headers should resolve the 403 issue. If it still doesn't work, check if your IP is blocked (unlikely if the browser works) or if your API key has restricted permissions.

内容的提问来源于stack exchange，提问作者Raúl Andrés Sira Alvarez