Tablets are rendering mobile sites instead of standard

[jbart08]

I've found in testing that tablet devices (iPad, iPad2, Samsung Galaxy 10") are going to the mobile version of our sites rather than the standard site versions. Is there a central location that allows you to define what version to serve up to a tablet device? I've grabbed the latest wurfl xml and patch file as of yesterday morning.

[luca.passani]

WURFL comes with a nice "is_tablet" capability. You can use that to decide which treat should be reserved to tablets.

Some consider them mobile devices. Others consider them fully-fledged web browser. Others still cannot simply direct tablets to their websites because iPads lack flash support.

At the end of the day, only the content owner knows what it is best for its users and for its business model. WURFL helps supporting whatever choice the content owner is most happy with.

Luca

[jbart08]

I get that, but the default configuration of the Java solution we have implemented is making that decision for me right now. I'd like to know where the setting(s) is/are that will allow me to specify the action to take for Tablets

[luca.passani]

which capabilities are you using to detect mobile vs web?

WURFL assumes that a tablet is a mobile device. If you don't like that, you'll need to make your app smarter and exploit the is_tablet option.

Which API are you using? can you post some code?

Luca

[jbart08]

I'm using the JAVA API with the following settings in my web.xml file. Let me know if I can provide more, and thanks for the help:


<web-app>
<display-name>www.XXXXXXXXXXX.edu</display-name>
<context-param>
<param-name>wurfl</param-name>
<param-value>/WEB-INF/wurfl-latest.zip</param-value>
</context-param>
<context-param>
<param-name>wurflPatch</param-name>
<param-value>/WEB-INF/wurfl_patch.xml</param-value>
</context-param>
<filter>
<filter-name>TrackingFilter</filter-name>
<filter-class>edu.XXXXXXXXXXX.web.filter.TrackingFilter</filter-class>
<init-param>
<param-name>domain</param-name>
<param-value>.XXXXXXXXXXX.edu</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>TrackingFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
<listener>
<listener-class>
net.sourceforge.wurfl.core.web.WURFLServletContextListener
</listener-class>
</listener>
<servlet>
<servlet-name>DeviceServlet</servlet-name>
<display-name>DeviceServlet</display-name>
<description/>
<servlet-class>edu.XXXXXXXXXXX.web.servlets.DeviceServlet</servlet-class>
<init-param>
<param-name>mobileUrl</param-name>
<param-value>http://dev-m.XXXXXXXXXXX.edu/</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>DeviceServlet</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
<error-page>
<error-code>404</error-code>
<location>/error.jsp</location>
</error-page>
<error-page>
<error-code>500</error-code>
<location>/error.jsp</location>
</error-page>
</web-app>

[luca.passani]

it seems to me that the magic is happening in TrackingFilter.java.

What's XXXXXX.edu? sounds like a fun educational institution to attend...

Luca

[jbart08]

TrackingFilter.java is an existing code class set for some site features unrelated to our WURFL. I went ahead and verified it's not doing anything with the mobile filter, it only deals with our persistent cookie and querystring reads for tracking site users and search engines.

Yup, it's a fine University

[luca.passani]

what about DeviceServlet.java?

[jbart08]

Sorry for the delay, I've had some progress and then a dead end. I've been able to isolate the Tomcat "welcome-file-list" is conflicting with the redirect in some way. When I remove the default file orders everything works, but when I put it back in the redirect never seems to occur. Seems like Tomcat's not playing well with our redirect code.

[jbart08]

Turns out my issue was that DeviceServlet was never checked into source control. Once we got it back, I'm able to program against tablet devices.... D'OH!