简体   繁体   English

为什么我的iPhone应用程序的Web服务调用仅在AT&T 4g LTE上失败?

[英]Why does my iPhone app's web service call fail on AT&T 4g LTE only?

I have an iPhone application that makes a few web service calls. 我有一个iPhone应用程序,可以进行一些Web服务调用。 There are 2 calls to simple RSS feeds and then there are 2 calls made to an ASP.NET powered web service. 有2个调用简单的RSS feed,然后有2个调用基于ASP.NET的Web服务。

The calls to the RSS feed work consistently in every scenario whether it is via wifi or 4g, and it also works for every carrier (AT&T, Sprint, Verizon, etc...). 无论是通过wifi还是4g,对RSS feed的调用在每种情况下均能始终如一地工作,并且也适用于每种运营商(AT&T,Sprint,Verizon等)。

The 2 calls made to the ASP.NET web service will always work on wifi, but they will not work on 4g with every carrier. 对ASP.NET Web服务的2个调用将始终在wifi上有效,但在每个运营商的4g上均不起作用。 Specifically AT&T 4g LTE will fail on these calls immediately every single time whereas calls made by another carrier (CSpire) will succeed on 4g. 具体来说,AT&T 4g LTE每次都会立即在这些呼叫上失败,而另一个运营商(CSpire)进行的呼叫将在4g上成功。

I want to clarify that iPhones using the same version of the app will succeed when requesting the ASP.NET calls via wifi, but will fail only when using AT&T 4g LTE. 我想澄清的是,使用相同版本应用程序的iPhone通过wifi请求ASP.NET调用时将成功,但仅在使用AT&T 4g LTE时才会失败。 I have tested them myself with "full bars" (full network service access) immediately after visiting websites on 4g. 访问4g网站后,我立即用“ full bar”(完全网络服务访问权限)对它们进行了测试。

I do not have access to any error messages as I do not personally own an iPhone with AT&T as its carrier. 我没有任何错误消息,因为我个人没有拥有以AT&T为载体的iPhone。

I've looked online and haven't found any issues related to a specific carrier like this. 我在网上看过,但没有发现与特定载体类似的任何问题。 Has anyone ever heard of this before? 有人听说过吗?

EDIT: I have not been able to test the iPhone app on a device with T-Mobile as the carrier, but I have learned that AT&T and T-Mobile use GSM while the other carriers use CDMA. 编辑:我无法在以T-Mobile为载体的设备上测试iPhone应用程序,但是我了解到AT&T和T-Mobile使用GSM,而其他运营商使用CDMA。 Could this be a determining factor? 这可能是决定因素吗?

I ran into a very similar issue with a project I'm working on. 我正在从事的项目遇到一个非常相似的问题。 The project uses authenticated soap web services that are implemented in ASP.net. 该项目使用在ASP.net中实现的经过身份验证的肥皂Web服务。

The problem ended up being that AT&T has an http proxy. 问题最终是AT&T有一个http代理。 I was accessing the authentication web service through http so it was being proxied. 我正在通过http访问身份验证Web服务,因此已被代理。 The call to subsequent services was being done over https (which can't be proxied) so the authentication token I received over http was not valid. 对后续服务的调用是通过https(无法代理)完成的,因此我通过http收到的身份验证令牌无效。 Switching all the service calls to https (including authentication) fixed the issue for me. 将所有服务调用都切换到https(包括身份验证)可以解决我的问题。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM