WAP 1.x 设备可以查看 WAP 2 或完整的 HTML 网站吗？
我认为这是不可能的，但是 WAP 1.x 设备可以查看 WAP 2 网站吗？或者甚至是完整的 HTML 网站？我的问题特别涉及旧手机（例如， http://www.gsmarena.com/ericsson_t20s-211 .php），但没有比 WAP 1.x 更好的浏览功能。
请记住，这是 WAP 1.x，与 WAP 2 不同，它不基于 HTTP。
I don't think this is possible, but can a WAP 1.x device view WAP 2 websites? Or even full HTML websites? My question specifically refers to older phones (e.g., http://www.gsmarena.com/ericsson_t20s-211.php) without better browsing capabilities than WAP 1.x.
Keep in mind this is WAP 1.x which isn't based on HTTP, as opposed to WAP 2.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
答案不是明确的是或否，而是取决于具体的设备。
就您提到的爱立信T20而言，它是NO。查看 WURFL 数据库 (http://wurfl.sourceforge.net/) 表明该设备不支持 XHTML ，并且它实际上偏爱 WML 1.1。这表明它甚至不支持最新的 WAP 1.x 标准（WAP 2000 年 6 月发布，通常称为 WAP 1.2.1，它使用 WML 1.3 标记），而是较旧的 WAP 1.1 设备。
但是，某些 WAP 1.x 设备可能可以查看 WAP 2 网站，具体取决于设备开发人员如何实现浏览器。唯一确定的方法是查看设备通过 HTTP 标头指示的内容类型。
WAP 1.x 设备无法直接与 Web 服务器通信，因为它不支持传统的 TCP/IP 堆栈，因此它必须通过 WAP 网关。但这并不妨碍 WAP 1.x 设备支持更高级的标记格式，例如 WAP 2（XHTML 移动配置文件 + 无线 CSS）、iMode (cHTML) 或 HTML 的某些子集等。
其中一个例子是 Openwave v6 浏览器，常用于许多WAP手机。该浏览器可以支持 WAP 1.x 和 WAP 2，以及上面指出的标记格式。如果设备开发人员决定不使用 TCP/IP 堆栈（较低的开发工作量、较低的许可成本、较低的带宽需求等），则设备将仅限于使用 WAP 1.x 协议堆栈，并且必须通过 WAP 网关与网络服务器通信。但它仍然可以处理更高级的标记格式。
The answer is not a clear yes or no, but rather that it depends upon the specific devices.
In the case of the Ericsson T20 that you mentioned, it is a NO. Looking at the WURFL database (http://wurfl.sourceforge.net/) indicates this device does not support XHTML, and that it actually has a preference for WML 1.1. This suggests that it does not even support the latest WAP 1.x standards (WAP June 2000 Release, commonly referred to as WAP 1.2.1, which uses WML 1.3 markup), but is an older WAP 1.1 device.
However, some WAP 1.x devices possibly could view WAP 2 websites, depending upon how the device developer implemented the browser. The only way to tell definitively is to look at the content types that the device indicates via HTTP headers.
A WAP 1.x device cannot communicate directly with a web server because it does not support a conventional TCP/IP stack, hence it must go via a WAP Gateway. But that does not preclude the WAP 1.x device from supporting more advanced markup formats such as WAP 2 (XHTML Mobile Profile + Wireless CSS), iMode (cHTML) or some subset of HTML etc.
One example of this is the Openwave v6 browser, commonly used in many WAP phones. This browser can support both WAP 1.x and WAP 2, and the markup formats indicated above. If the device developer decided not to use a TCP/IP stack (lower development effort, lower license costs, lower bandwidth required etc) then the device would be limited to using the WAP 1.x protocol stacks, and must go via a WAP Gateway to communicate with the web server. But it could still handle the more advanced markup formats.
答案是否定的。
看一下手机并看看屏幕尺寸，事实上它甚至都不是彩色的，您如何期望它能够远程显示 Full HTML 或 WAP 2 的内容？
The answer is simply no.
Take a look at the phone and look at the screen size the fact that it isn't even color how do you expect it to display any thing that is remotely Full HTML or WAP 2?
可以通过 WAP 网关显示原始页面/站点的转换形式，该网关将服务器的 HTTP/S 通信转换为 WAP 1，反之亦然将手机的 WAP 1 转换为 HTTP/S：
http://www.thewirelessfaq.com/how_does_a_wap_device_connect_to_the_internet
对用户来说是透明的（除了页面丑陋之外） ），所以看起来他们实际上有一个 HTTP/S 浏览器——而事实上他们没有。
It's possible to display a converted form of the original page/site via WAP gateways which translate a server's HTTP/S communication to WAP 1 and conversely a phone's WAP 1 to HTTP/S:
http://www.thewirelessfaq.com/how_does_a_wap_device_connect_to_the_internet
It's transparent to the users (aside from the pages being ugly), so it seems like they actually have an HTTP/S browser--when they in fact do not.