If the actual download is done by a different application, there is
not much you can do with headers.
What you *can* do is redirect the download to a unique, time-limited
URL, which encodes the necessary information.
So you'd have something like:
- Application authenticates the user, the user browses for and pays for
content.
- The server generates a unique URL, that have parts that uniquely
identify the user (e.g.
http://yourserver.com/download/0x76248ABC287348CBD919023/OppsIDidItAgain.mp3
)
- This URL with the authentication key is what the download application
sees (I assume it's the web browser).
- While serving a request for such URL, the server extracts the key and
verifies its validity.
- Have a way on the server to expire authentication keys, or encode
their time limit right in their value, so that authenticated links can't
be shared. The former is more secure.
-- Kostya
23.09.2010 20:06, Marxvox пишет:
Hi everyone,
I am trying to find the best way to consistently identify a unique
subscriber using an Android phone to download content like ringtones,
wallpaper, games, etc. When an Android phone browses my web-based
content storefront using the phone's browser over 3G, I am able to get
the phone number from the headers sent to my server. However, when a
content download begins, the phone retrieves the content using a
different application, and therefore does not send the same headers
and does not maintain the same HTTP session, preventing me from
getting the phone number and preventing me from seeing this phone as
the same subscriber that was browsing earlier. Is there any other way
to uniquely identify the subscriber on the server-side when this
happens? Any insight would be greatly appreciated. Thanks!
--
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
