You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Jeremy Thomerson <je...@wickettraining.com> on 2009/02/11 08:50:18 UTC

Re: Problem with WebRequestCodingStrategy's and mobile phones

Can one of the core devs add a note to the javadoc of
UrlCompressingWebCodingStrategy to the effect of "NOTE: Using this strategy
may cause errors in some mobile phone browsers, specifically the Motorola V3
and other UP.Link browser mobile phones"....


-- 
Jeremy Thomerson
http://www.wickettraining.com

On Mon, Feb 9, 2009 at 2:11 PM, Jeremy Levy <je...@meetmoi.com> wrote:

> We figured out something very interesting with the default URL coding
> strategy's that Wicket uses when using mobile phones / devices.
>
> We run a fairly heavily trafficked mobile site, and having been using
> CryptedUrlWebRequestCodingStrategy for sometime.  While attempting to debug
> some page timeout issues we switched to UrlCompressingWebCodingStrategy and
> we started getting compaints from users that they were getting HTTP error
> 400's.
>
> We were able to repeat the error locally, it happened only when using some
> specific phones and mobile browsers.  Specifically on the Motorola V3
> (useragent: MOT-V3re/0E.40.29R MIB/2.2.1 Profile/MIDP-2.0
> Configuration/CLDC-1.1 UP.Link/6.3.1.20.06.3.1.20.0) and other UP.Link
> browser moble phones.  We noticed that when the user got the 400 error
> there
> was nothing in our tomcat logs, or even in our apache logs.
>
> Switching to standard WebRequestCodingStrategy had the same issue.  I
> suspect that there are some characters in the form submit url ( :'s ?) that
> this crappy browser can't figure out to post to.  Swiching back to
> CryptedUrlWebRequestCodingStrategy fixed the problem.
>
> We tested this on several other handsets that we have available and can
> confirm that it breaks all form submits.
>
> This is a some what obsecure case, and perhaps irrelvant if you don't run a
> mobile site, but we saw our number's drop by about 20% - 50% until we
> figured this out.
>
> Hope this helps someone else.
>
> Jeremy
>
> --
> Jeremy Levy
>
> See my location in real-time:
> http://seemywhere.com/jeremy
>

Re: Problem with WebRequestCodingStrategy's and mobile phones

Posted by Igor Vaynberg <ig...@gmail.com>.
we would have to add it to almost all coding strategies because almost
all of them use the colon.

-igor

On Tue, Feb 10, 2009 at 11:50 PM, Jeremy Thomerson
<je...@wickettraining.com> wrote:
> Can one of the core devs add a note to the javadoc of
> UrlCompressingWebCodingStrategy to the effect of "NOTE: Using this strategy
> may cause errors in some mobile phone browsers, specifically the Motorola V3
> and other UP.Link browser mobile phones"....
>
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
> On Mon, Feb 9, 2009 at 2:11 PM, Jeremy Levy <je...@meetmoi.com> wrote:
>
>> We figured out something very interesting with the default URL coding
>> strategy's that Wicket uses when using mobile phones / devices.
>>
>> We run a fairly heavily trafficked mobile site, and having been using
>> CryptedUrlWebRequestCodingStrategy for sometime.  While attempting to debug
>> some page timeout issues we switched to UrlCompressingWebCodingStrategy and
>> we started getting compaints from users that they were getting HTTP error
>> 400's.
>>
>> We were able to repeat the error locally, it happened only when using some
>> specific phones and mobile browsers.  Specifically on the Motorola V3
>> (useragent: MOT-V3re/0E.40.29R MIB/2.2.1 Profile/MIDP-2.0
>> Configuration/CLDC-1.1 UP.Link/6.3.1.20.06.3.1.20.0) and other UP.Link
>> browser moble phones.  We noticed that when the user got the 400 error
>> there
>> was nothing in our tomcat logs, or even in our apache logs.
>>
>> Switching to standard WebRequestCodingStrategy had the same issue.  I
>> suspect that there are some characters in the form submit url ( :'s ?) that
>> this crappy browser can't figure out to post to.  Swiching back to
>> CryptedUrlWebRequestCodingStrategy fixed the problem.
>>
>> We tested this on several other handsets that we have available and can
>> confirm that it breaks all form submits.
>>
>> This is a some what obsecure case, and perhaps irrelvant if you don't run a
>> mobile site, but we saw our number's drop by about 20% - 50% until we
>> figured this out.
>>
>> Hope this helps someone else.
>>
>> Jeremy
>>
>> --
>> Jeremy Levy
>>
>> See my location in real-time:
>> http://seemywhere.com/jeremy
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org