On Mon, Jan 31, 2011 at 4:13 PM, WiViu Technologies <wiviut...@gmail.com> wrote:
> We are trying to develop an Android App which uses raw HTTP APIs for
> login to a website. We are then using WebView & other HTTP APIs to
> upload and download files from the website. The problem is that
> WebView, and the subsequent calls using HTTP APIs, fail because the
> website does not see the cookies. WebView simply lands to login page.

WebView maintains an entirely separate cookie store than does any
HttpClient instance.

> Have you experienced a similar issue before?  Else would you know how
> to get around this issue?  If so please contact us, or reply to this
> post, on how we could solve this.

Either:

a. Be consistent on the technology you use, or

b. Manually schlep cookies between WebView and each HttpClient instance

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Android Training in London: http://bit.ly/smand1 and http://bit.ly/smand2

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to