SOAP API返回HTML而非XML求助：Postman正常但移动端异常

Hey David, I’ve run into exactly this kind of Postman vs mobile app SOAP mismatch before—let’s break down the most likely fixes for why your app is getting HTML instead of XML, and why your PHP function isn’t firing.

1. Fix Request Headers (The #1 Cause of This Discrepancy) #

Postman automatically sets proper headers for SOAP requests, but mobile apps don’t do this by default. If your request is missing critical headers, the server will default to returning HTML error pages instead of processing your SOAP call.

Add these headers to your loginRequest method’s NSMutableURLRequest:

NSMutableURLRequest *request = [NSMutableURLRequest requestWithURL:yourApiUrl];
// Tell the server you're sending valid SOAP XML
[request setValue:@"text/xml; charset=utf-8" forHTTPHeaderField:@"Content-Type"];
// Explicitly request XML in the response
[request setValue:@"text/xml" forHTTPHeaderField:@"Accept"];

2. Verify Your API URL Matches Postman Exactly #

Even tiny differences between your app’s URL and Postman’s can send your request to a static HTML page instead of your SOAP endpoint. Check for:

• Missing .php suffix (e.g., /soapapi instead of /soapapi.php)
• HTTP vs HTTPS mismatch
• Wrong port number
• Typos in the path

Print the URL in your app to cross-check:

NSLog(@"API Request URL: %@", yourApiUrl.absoluteString);

Compare this directly to the URL in Postman’s address bar—no mistakes allowed!

3. Replicate Postman’s Authentication Logic #

If your Opencast API requires auth, Postman might be storing cookies or using Basic Auth that your app isn’t replicating. For example, if using Basic Auth, add the authorization header manually:

NSString *credentials = [NSString stringWithFormat:@"%@:%@", yourUsername, yourPassword];
NSData *credentialData = [credentials dataUsingEncoding:NSUTF8StringEncoding];
NSString *base64Credentials = [credentialData base64EncodedStringWithOptions:0];
NSString *authHeader = [NSString stringWithFormat:@"Basic %@", base64Credentials];
[request setValue:authHeader forHTTPHeaderField:@"Authorization"];

If the API uses session cookies, make sure your app’s NSURLSession is preserving cookies between requests (Postman does this automatically).

4. Validate Your SOAP Request Body #

A malformed XML request will cause the server to reject your call and return an HTML error. Print the full XML your app is sending:

NSString *soapBody = @"Your generated SOAP XML string here";
NSLog(@"SOAP Request Body: %@", soapBody);

Copy this exact XML into Postman’s request body and send it—if it fails here too, you know the issue is with your XML formatting (like unescaped special characters: &, <, >). Fix those before testing again in the app.

5. Check Server Logs for Hard Clues #

If none of the above works, dive into your server’s access and error logs. They’ll show:

• Whether your request actually reached the correct PHP file
• If the server returned a 404, 401, or 500 error
• Any PHP errors that aren’t showing up in your app’s HTML response

Server logs are often the fastest way to figure out why your PHP function isn’t triggering.

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