WURFL 未成功检测到 FireFox 4

发布于 2024-10-27 20:06:07 字数 389 浏览 6 评论 0原文

我正在使用名为 FiftyOne Degrees (http://51 Degrees.mobi) 的第 3 方应用程序进行设备检测。

该应用程序使用 WURFL (http://wurfl.sourceforge.net/) 来查找请求的设备类型基于用户代理的页面。

除了在新的 Fire Fox 4 中之外,这效果很好。我认为这是因为 FF4 于 2011 年 3 月 22 日发布,而 WURFL 上次更新于 2011 年 3 月 6 日。

还有其他人遇到过这个问题吗?有什么解决方法吗?

I'm using an 3rd party application for device detection called FiftyOne Degrees (http://51degrees.mobi).

That application uses WURFL (http://wurfl.sourceforge.net/) to find out what type of device requested the page based on the user agent.

This works great, except for in the new Fire Fox 4. I think this is because FF4 was released on the 22nd March 2011 while the WURFL was last updated on the 6th March 2011.

Has anyone else come across this problem? Any work arounds?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

孤檠 2024-11-03 20:06:07

您可能还需要重建 FiftyOne.Foundation.dll,源代码可以在这里找到:

http://51 Degrees.codeplex.com/

有了新的 dll 并在 App_Data 文件夹中更新了 web_browsers_patch.xml,我就能够解决我的 FF4 移动重定向问题。

这是我使用的 XML:

<device user_agent="Firefox/4.0" fall_back="firefox" id="firefox_4">
  <group id="product_info">
    <capability name="model_name" value="4.0" />
  </group>
</device>

我使用的是旧版本的 DLL,仅靠 XML 不足以让 FF4 被识别。

You may also need to rebuild FiftyOne.Foundation.dll, source can be found here:

http://51degrees.codeplex.com/

With the new dll in place and the updated web_browsers_patch.xml in the App_Data folder I was able to resolve my FF4 mobile redirection issues.

This is the XML I used:

<device user_agent="Firefox/4.0" fall_back="firefox" id="firefox_4">
  <group id="product_info">
    <capability name="model_name" value="4.0" />
  </group>
</device>

I was using an old version of the DLL and the XML alone was not enough to get FF4 recognized.

稍尽春風 2024-11-03 20:06:07

我认为最简单的方法是查看网络浏览器的 wurl 补丁文件。 (http://wurfl.sourceforge.net/web_browsers_patch.xml) 它包含了人们通常使用的所有浏览器。您的 App_Data 文件夹中应该有此文件。
您应该能够引用 Firefox 4 来更新您的补丁文件,并声明后备浏览器类型。

我正在使用此处找到的用户代理字符串: http://hacks.mozilla.org/2010/09/final-user-agent-string-for-firefox-4/

<device user_agent="Firefox/3.5" fall_back="firefox" id="firefox_3_5">
 <group id="product_info">
  <capability name="model_name" value="3.5"/>
 </group>
</device>

可以更改为:

<device user_agent="Firefox/4.0" fall_back="firefox" id="firefox_4_0">
 <group id="product_info">
  <capability name="model_name" value="4.0"/>
 </group>
</device>

我以前没有遇到过这个问题,但这是我会处理你的问题的方式。
希望这有帮助:)

I think the easiest way would be to look at the web browsers patch file for wurl. (http://wurfl.sourceforge.net/web_browsers_patch.xml) It contains all the browsers that people usually use. You should have this file in your App_Data folder.
You should be able to just update your patch file with a reference to firefox 4, and declare a fallback browser type.

I'm using the user agent string found here: http://hacks.mozilla.org/2010/09/final-user-agent-string-for-firefox-4/

<device user_agent="Firefox/3.5" fall_back="firefox" id="firefox_3_5">
 <group id="product_info">
  <capability name="model_name" value="3.5"/>
 </group>
</device>

could change to:

<device user_agent="Firefox/4.0" fall_back="firefox" id="firefox_4_0">
 <group id="product_info">
  <capability name="model_name" value="4.0"/>
 </group>
</device>

I haven't had this issue before, but this is the way I would approach your issue.
Hope this helps :)

裸钻 2024-11-03 20:06:07

这是我发现对我有用的解决方法。

我将以下内容添加到 web_browsers_patch.xml 然后执行 iisreset。

  <!-- work around -->
    <device user_agent="Firefox/4.0" fall_back="firefox" id="firefox_4">
      <group id="product_info">
        <capability name="model_name" value="4"/>
        <capability name="is_wireless_device" value="false"/>
      </group>
    </device>
    <device user_agent="Firefox/4.0" fall_back="firefox" id="sony_mylo_ver1_sub1" >
      <group id="product_info">
        <capability name="model_name" value="4"/>
      </group>
    </device>
    <device user_agent="Firefox/4.0" fall_back="firefox" id="sony_mylo_ver1" >
      <group id="product_info">
        <capability name="model_name" value="4"/>
      </group>
    </device>
    <device user_agent="Firefox/4.0" fall_back="firefox" id="stupid_novarra_proxy_sub73" >
      <group id="product_info">
        <capability name="model_name" value="4"/>
      </group>
    </device>
  <!-- end work around -->

Here's the workaround that I found worked for me.

I added the following to the web_browsers_patch.xml then did an iisreset.

  <!-- work around -->
    <device user_agent="Firefox/4.0" fall_back="firefox" id="firefox_4">
      <group id="product_info">
        <capability name="model_name" value="4"/>
        <capability name="is_wireless_device" value="false"/>
      </group>
    </device>
    <device user_agent="Firefox/4.0" fall_back="firefox" id="sony_mylo_ver1_sub1" >
      <group id="product_info">
        <capability name="model_name" value="4"/>
      </group>
    </device>
    <device user_agent="Firefox/4.0" fall_back="firefox" id="sony_mylo_ver1" >
      <group id="product_info">
        <capability name="model_name" value="4"/>
      </group>
    </device>
    <device user_agent="Firefox/4.0" fall_back="firefox" id="stupid_novarra_proxy_sub73" >
      <group id="product_info">
        <capability name="model_name" value="4"/>
      </group>
    </device>
  <!-- end work around -->
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文