05.02.2011 20:19, Jan Westin пишет:
Thanks fot the tip.
Welcome.
But in this case the goal is to provide users with an unique hash and
to validate their handsets to get access to a newspapers standing
subscriber-feed.
Thus the parameter is intended for one time use.
So what? URL rewriting is a general scheme, you can use it with any
parameters or values you like:
http://www.site.com/validate/0x01234567
http://www.site.com/validate/0x89ABCDEF
or even this :)
http://www.site.com/check01234567user89ABCDEFsubscription
With this Apache module, you can make it transparent for the web server
code. I'm sure there are solution for other platforms (IIS, WebSphere,
etc.) as well:
http://httpd.apache.org/docs/current/mod/mod_rewrite.html
-- Kostya
The link is retrieved from our SMSC by sending a keyword to a known
shortcode.
//Jan
On Feb 5, 5:40 pm, Kostya Vasilyev<[email protected]> wrote:
BTW, it's been suggested to use a link shortening service - that would
break intent filters, if they are used to launch the application.
What would work, is to use URL rewriting, so rather than using:
http://www.site.com/page?param=value
one would use something like:
http://www.site.com/page/param/value
A rewritten URL like the above would still work with intent filters to
launch the application, if that's the goal.
-- Kostya
05.02.2011 18:25, kernelpanic пишет:
You didn't mention which Galaxy S phone or if it's all of them.
FWIW, I've had no issues sending this type of URL through an SMS
gateway to the Samsung Epic Galaxy class phone - works as expected.
I do question the validity of the spaces in the query and suspect that
is the issue here.
I can send you a screen shot from an Epic showing my links versus your
links - mine look fine, yours look like your image.
I also sent the same text message to a diff phone (J2ME based) and the
link is underlined up to the first space but it includes the ?
sc=4KNZNSEN part in the link
Loosely related - in the past, I have had issues with some phones/
carriers when the URL string is rather long. There is the obvious
inherent SMS length limitations, but even when that is complied with,
I have seen some devices that accept the URL in the SMS, but then
truncate it between the SMS and the browser when the link is tapped -
some as short as 60 characters, some at 64 characters, some not at
all. However, I don't think that is the problem here since you are
saying it is happening at the "?"
On Feb 2, 3:51 am, Jan Westin<[email protected]> wrote:
Hi,
Has anyone else stumbled upon a similar issue as seen in the following
screen shot :http://twitpic.com/3vpnzx
The problem is when a user sends a URL containing a query string, the
query string is not interpreted as part of the URL.
I've seen this happen to both my HTC Desire running 2.2 and on Samsung
galaxy S phones.
Does anyone know of a workaround or a fix for this?
//Jan
--
Kostya Vasilyev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com
--
Kostya Vasilyev -- WiFi Manager + pretty widget -- http://kmansoft.wordpress.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
