"failed: network login?" error with collect 1.1.7

Hi,

I have a custom php script for submission on the server that worked
perfectly with ODK Collect 1.1.5. Now I've upgraded to Collect 1.1.7
and I get this error when submitting the form:

failed: network login?

What has been changed in the protocol?

This is if the server doesn't require authentication. If the server does
require authentication and I configure the user and password in ODK
Collect, then I don't get this error any more, but it hangs at "Sending
form..." forever (definitely a bug, no matter how wrong the response
from the server is, the client should at the very least have a timeout).

Is there ANY documentation about the ODK client-server protocol?

thanks
m.

··· On 09/24/2011 02:27 PM, Matteo Sisti Sette wrote: > Hi, > > I have a custom php script for submission on the server that worked > perfectly with ODK Collect 1.1.5. Now I've upgraded to Collect 1.1.7 > and I get this error when submitting the form: > > failed: network login?

openrosa apihttps://bitbucket.org/javarosa/javarosa/wiki/AuthorizationAPIhttps://bitbucket.org/javarosa/javarosa/wiki/OpenRosaRequest

collect codehttp://code.google.com/p/opendatakit/source/browse/src/org/odk/collect/android/tasks/DownloadFormListTask.java?repo=collecthttp://code.google.com/p/opendatakit/source/browse/src/org/odk/collect/android/tasks/DownloadFormsTask.java?repo=collecthttp://code.google.com/p/opendatakit/source/browse/src/org/odk/collect/android/utilities/WebUtils.java?repo=collect

··· On Sat, Sep 24, 2011 at 16:56, Matteo Sisti Sette wrote: > On 09/24/2011 02:27 PM, Matteo Sisti Sette wrote: >> >> Hi, >> >> I have a custom php script for submission on the server that worked >> perfectly with ODK Collect 1.1.5. Now I've upgraded to Collect 1.1.7 >> and I get this error when submitting the form: >> >> failed: network login? > > This is if the server doesn't require authentication. If the server does > require authentication and I configure the user and password in ODK Collect, > then I don't get this error any more, but it hangs at "Sending form..." > forever (definitely a bug, no matter how wrong the response from the server > is, the client should at the very least have a timeout). > > Is there ANY documentation about the ODK client-server protocol? > > thanks > m. > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

Thank you

How can I find out which authentication mechanism my server is using?
(it's an apache web server on which I'm trying to use php to receive the
data - which I btw I had already got to work with odk collect 1.1.5)

Maybe my problem is that I am using "basic" authentication on http (not
https) while the protocol requires either RFC2617 Digest Authentication
or basic authentication on https??

Anyway I don't understand why ODK Collect hangs forever on "Sending
form" instead of giving a meaningful error message...

thanks
m.

··· On 09/24/2011 04:22 PM, Yaw Anokwa wrote: > # openrosa apihttps://bitbucket.org/javarosa/javarosa/wiki/AuthorizationAPIhttps://bitbucket.org/javarosa/javarosa/wiki/OpenRosaRequest > # collect codehttp://code.google.com/p/opendatakit/source/browse/src/org/odk/collect/android/tasks/DownloadFormListTask.java?repo=collecthttp://code.google.com/p/opendatakit/source/browse/src/org/odk/collect/android/tasks/DownloadFormsTask.java?repo=collecthttp://code.google.com/p/opendatakit/source/browse/src/org/odk/collect/android/utilities/WebUtils.java?repo=collect > > > On Sat, Sep 24, 2011 at 16:56, Matteo Sisti Sette wrote: >> On 09/24/2011 02:27 PM, Matteo Sisti Sette wrote: >>> >>> Hi, >>> >>> I have a custom php script for submission on the server that worked >>> perfectly with ODK Collect 1.1.5. Now I've upgraded to Collect 1.1.7 >>> and I get this error when submitting the form: >>> >>> failed: network login? >> >> This is if the server doesn't require authentication. If the server does >> require authentication and I configure the user and password in ODK Collect, >> then I don't get this error any more, but it hangs at "Sending form..." >> forever (definitely a bug, no matter how wrong the response from the server >> is, the client should at the very least have a timeout). >> >> Is there ANY documentation about the ODK client-server protocol? >> >> thanks >> m. >> >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> >

we have changed the protocol between 1.1.5 and 1.1.7 to support auth.

i don't know what protocol your server is using, perhaps try wireshark
or charles proxy to read your headers to figure that out.

collect takes a long time to timeout because most of our users are on
unreliable connections where longer timeouts are needed. that's why
the connection seems to hang.

if you need more detailed error messages, we try to print them to the
log (run adb logcat). you can also add them to the collect source. we
don't bubble them up to the ui because "socket timeout exception"
isn't exactly user friendly.

··· On Sat, Sep 24, 2011 at 17:37, Matteo Sisti Sette wrote: > Thank you > > How can I find out which authentication mechanism my server is using? (it's > an apache web server on which I'm trying to use php to receive the data - > which I btw I had already got to work with odk collect 1.1.5) > > Maybe my problem is that I am using "basic" authentication on http (not > https) while the protocol requires either RFC2617 Digest Authentication or > basic authentication on https?? > > Anyway I don't understand why ODK Collect hangs forever on "Sending form" > instead of giving a meaningful error message... > > thanks > m. > > On 09/24/2011 04:22 PM, Yaw Anokwa wrote: >> >> # openrosa >> apihttps://bitbucket.org/javarosa/javarosa/wiki/AuthorizationAPIhttps://bitbucket.org/javarosa/javarosa/wiki/OpenRosaRequest >> # collect >> codehttp://code.google.com/p/opendatakit/source/browse/src/org/odk/collect/android/tasks/DownloadFormListTask.java?repo=collecthttp://code.google.com/p/opendatakit/source/browse/src/org/odk/collect/android/tasks/DownloadFormsTask.java?repo=collecthttp://code.google.com/p/opendatakit/source/browse/src/org/odk/collect/android/utilities/WebUtils.java?repo=collect >> >> >> On Sat, Sep 24, 2011 at 16:56, Matteo Sisti Sette wrote: >>> >>> On 09/24/2011 02:27 PM, Matteo Sisti Sette wrote: >>>> >>>> Hi, >>>> >>>> I have a custom php script for submission on the server that worked >>>> perfectly with ODK Collect 1.1.5. Now I've upgraded to Collect 1.1.7 >>>> and I get this error when submitting the form: >>>> >>>> failed: network login? >>> >>> This is if the server doesn't require authentication. If the server does >>> require authentication and I configure the user and password in ODK >>> Collect, >>> then I don't get this error any more, but it hangs at "Sending form..." >>> forever (definitely a bug, no matter how wrong the response from the >>> server >>> is, the client should at the very least have a timeout). >>> >>> Is there ANY documentation about the ODK client-server protocol? >>> >>> thanks >>> m. >>> >>> -- >>> Post: opendatakit@googlegroups.com >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>> Options: http://groups.google.com/group/opendatakit?hl=en >>> >> > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

collect takes a long time to timeout because most of our users are on
unreliable connections where longer timeouts are needed. that's why
the connection seems to hang.

I see. Anyway in this case I can't see how a timeout can happen at all.
If the server is not using the correct security or whatever, the client
should be able to detect it and stop waiting, shouldn't it?

if you need more detailed error messages, we try to print them to the
log (run adb logcat).

I installed the Log Collector application recommended by somebody in
this list and sent myself some logs but there's nothing apparently
related to odk collect in there...... what am I missing?

we
don't bubble them up to the ui because "socket timeout exception"
isn't exactly user friendly.

Yes of course, I wouldn't expect such a message to be bubbled up to the
user as is, I would just expect some error message rather than waiting
forever.

Thanks
m.

··· On 09/24/2011 04:53 PM, Yaw Anokwa wrote:

hi matteo,

please submit a bug report or a patch if you feel what we have now
with the timeouts are not adequate.

if there are no useful debug messages when you use the logger, then i
encourage you to download the collect source and add some so you can
track down your issue.

yaw

··· On Sat, Sep 24, 2011 at 18:03, Matteo Sisti Sette wrote: > On 09/24/2011 04:53 PM, Yaw Anokwa wrote: > >> collect takes a long time to timeout because most of our users are on >> unreliable connections where longer timeouts are needed. that's why >> the connection seems to hang. > > I see. Anyway in this case I can't see how a timeout can happen at all. If > the server is not using the correct security or whatever, the client should > be able to detect it and stop waiting, shouldn't it? > >> if you need more detailed error messages, we try to print them to the >> log (run adb logcat). > > I installed the Log Collector application recommended by somebody in this > list and sent myself some logs but there's nothing apparently related to odk > collect in there...... what am I missing? > >> we >> >> don't bubble them up to the ui because "socket timeout exception" >> isn't exactly user friendly. > > Yes of course, I wouldn't expect such a message to be bubbled up to the user > as is, I would just expect _some_ error message rather than waiting forever. > > > Thanks > m. > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

Hi,

I don't understand whether basic authentication over http is expected to
work or not.

This seems to suggest it is:

"""
OpenRosa compliant devices MUST support both:
1.
the subset of RFC2617 Digest Authentication defined below and
2.
the Basic Authentication mechanism also outlined in RFC2617.

OpenRosa compliant servers MUST support at least one of either:
the subset of RFC2617 Digest Authentication defined below or
the Basic Authentication mechanism outlined in RFC2617.
"""

but this seems to suggest that Digest Authentication is required:

"""
device-and-server interactions for which the server requires
authentication MUST implement the OpenRosa Restricted Digest
authentication scheme as detailed below
"""

I'm using Basic authentication now on the server.

I have set up the server settings in ODK Collect with the username and
password; however, when I send a form, it asks me for the user and
password again. Then, after inserting them, it hangs forever at "sending
form".

By looking at the access log on the server, I see that when ODK issues
the HEAD request it gets a 401 response and then when it issues the POST
requests it gets 401 again.

Now I've tried to retrieve the form list, and it keeps asking me user
and password again and again.

So everything looks like as if i was not inserting the correct user and
password, but they ARE correct (I insert the same credentials from a
browser and they work)...... What else may I check out? I'm stuck...

··· On 09/24/2011 05:11 PM, Yaw Anokwa wrote: > hi matteo, > > please submit a bug report or a patch if you feel what we have now > with the timeouts are not adequate. > > if there are no useful debug messages when you use the logger, then i > encourage you to download the collect source and add some so you can > track down your issue. > > yaw > > On Sat, Sep 24, 2011 at 18:03, Matteo Sisti Sette wrote: >> On 09/24/2011 04:53 PM, Yaw Anokwa wrote: >> >>> collect takes a long time to timeout because most of our users are on >>> unreliable connections where longer timeouts are needed. that's why >>> the connection seems to hang. >> >> I see. Anyway in this case I can't see how a timeout can happen at all. If >> the server is not using the correct security or whatever, the client should >> be able to detect it and stop waiting, shouldn't it? >> >>> if you need more detailed error messages, we try to print them to the >>> log (run adb logcat). >> >> I installed the Log Collector application recommended by somebody in this >> list and sent myself some logs but there's nothing apparently related to odk >> collect in there...... what am I missing? >> >>> we >>> >>> don't bubble them up to the ui because "socket timeout exception" >>> isn't exactly user friendly. >> >> Yes of course, I wouldn't expect such a message to be bubbled up to the user >> as is, I would just expect _some_ error message rather than waiting forever. >> >> >> Thanks >> m. >> >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> >

Hi,

So I switched to https instead of http, and now the problem seems to be
the certificate. When I try to get new forms ODK Collect crashes; when I
try to send a form, I get a "generic exception". The logs show a
"javax.net.ssl.SSLPeerUnverifiedException: No peer certificate"
exception, that what makes me think the problem is with SSL certificates.

I currently have a self-signed certificate that i didn't create
myself, it was already installed by default on the server (it is
centOS+Plesk).

Do I need to pay more than $600 and obtain a Verisign signed certificate
in order to have ODK Collect be able to connect to the server? Or is
there a way I can tell Android (or ODK Collect) to trust my self signed
certificate?

Thanks
m.

Now I am using https on the server, with Basic Authentication:

  • when retrieving the form list, ODK Collect crashes

  • when submitting a form I get: "FAILED: generic exception. great"

Any idea?

··· On 09/24/2011 06:23 PM, Matteo Sisti Sette wrote: > I'm using Basic authentication now on the server. > > I have set up the server settings in ODK Collect with the username and > password; however, when I send a form, it asks me for the user and > password again. Then, after inserting them, it hangs forever at "sending > form". > > By looking at the access log on the server, I see that when ODK issues > the HEAD request it gets a 401 response and then when it issues the POST > requests it gets 401 again. > > Now I've tried to retrieve the form list, and it keeps asking me user > and password again and again. > > > So everything looks like as if i was not inserting the correct user and > password, but they ARE correct (I insert the same credentials from a > browser and they work)...... What else may I check out? I'm stuck... > > > > > On 09/24/2011 05:11 PM, Yaw Anokwa wrote: >> hi matteo, >> >> please submit a bug report or a patch if you feel what we have now >> with the timeouts are not adequate. >> >> if there are no useful debug messages when you use the logger, then i >> encourage you to download the collect source and add some so you can >> track down your issue. >> >> yaw >> >> On Sat, Sep 24, 2011 at 18:03, Matteo Sisti Sette wrote: >>> On 09/24/2011 04:53 PM, Yaw Anokwa wrote: >>> >>>> collect takes a long time to timeout because most of our users are on >>>> unreliable connections where longer timeouts are needed. that's why >>>> the connection seems to hang. >>> >>> I see. Anyway in this case I can't see how a timeout can happen at >>> all. If >>> the server is not using the correct security or whatever, the client >>> should >>> be able to detect it and stop waiting, shouldn't it? >>> >>>> if you need more detailed error messages, we try to print them to the >>>> log (run adb logcat). >>> >>> I installed the Log Collector application recommended by somebody in >>> this >>> list and sent myself some logs but there's nothing apparently related >>> to odk >>> collect in there...... what am I missing? >>> >>>> we >>>> >>>> don't bubble them up to the ui because "socket timeout exception" >>>> isn't exactly user friendly. >>> >>> Yes of course, I wouldn't expect such a message to be bubbled up to >>> the user >>> as is, I would just expect _some_ error message rather than waiting >>> forever. >>> >>> >>> Thanks >>> m. >>> >>> -- >>> Post: opendatakit@googlegroups.com >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >>> Options: http://groups.google.com/group/opendatakit?hl=en >>> >> >

we currently do not support self-signed certs in collect because it's
a fair bit of work.

if you want to read the discussion that we had on
opendatakit-developers@googlegroups.com, read
https://groups.google.com/d/topic/opendatakit-developers/i2aOhQ9Tjr8/discussion.

the relevant bug is http://code.google.com/p/opendatakit/issues/detail?id=279

··· On Sat, Sep 24, 2011 at 21:00, Matteo Sisti Sette wrote: > Hi, > > So I switched to https instead of http, and now the problem seems to be the > certificate. When I try to get new forms ODK Collect crashes; when I try to > send a form, I get a "generic exception". The logs show a > "javax.net.ssl.SSLPeerUnverifiedException: No peer certificate" exception, > that what makes me think the problem is with SSL certificates. > > I currently have a self-signed certificate that i didn't create myself, it > was already installed by default on the server (it is centOS+Plesk). > > Do I need to pay more than $600 and obtain a Verisign signed certificate in > order to have ODK Collect be able to connect to the server? Or is there a > way I can tell Android (or ODK Collect) to trust my self signed certificate? > > > Thanks > m. > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

So the only way to get ODK Collect to work with a custom server is to to
pay several hundreds dollars for a signed certificate?? Or is there such
a thing as a cheap non-self-signed certificate? (perhaps one signed by a
not-so-trusted CA whose certificate I may install on the device? or
something like that?)

Or is it actually possible to get authentication to work without ssl
(perhaps with Digest Authentication)? Or will that in turn also need a
certificate?

thanks
m.

··· On 09/24/2011 08:33 PM, Yaw Anokwa wrote: > we currently do not support self-signed certs in collect because it's > a fair bit of work.

So the only way to get ODK Collect to work with a custom server is to to pay
several hundreds dollars for a signed certificate?? Or is there such a thing
as a cheap non-self-signed certificate? (perhaps one signed by a
not-so-trusted CA whose certificate I may install on the device? or
something like that?)

you can either buy a cert (geo-trust is $149) or you can modify
android/collect to accept your cert (the bug i filed at
http://code.google.com/p/opendatakit/issues/detail?id=279 has links on
how to do that).

Or is it actually possible to get authentication to work without ssl
(perhaps with Digest Authentication)? Or will that in turn also need a
certificate?

https requires a certificate. as far as i know, digest has worked with
our gae and local servers in 1.1.7 over http. others have built
backends against the new api that have worked, so if it's not working,
the problem is likely with your backend.

if you file a bug with a way for us to reproduce what problems you are
having, we can take a look when we get some time. if this is an urgent
matter, i'm glad to recommend developers available for hire who can
help troubleshoot.

If you are using Basic authentication, you absolutely must use HTTPS; this
is because the username and password are sent as-is (unencrypted) to the
server with that authentication scheme. HTTPS encryptes the entire
transmission so nobody can eavesdrop. We assume that ports 443 and 8443 are
the only two ports used for HTTPS, so if you are using alternative ports,
ODK Collect will not send the username and password even if you enter it
into the phone. This is to avoid misconfigurations that might breach
security.

Digest authentication can use any port and does not require HTTPS because
the password is encrypted separately; but by not using HTTPS, your data will
be visible to eavesdroppers.

I believe we also do not allow the SSL certificate of the server to be
self-signed (since most users don't control their wireless access points,
doing so would allow anyone to claim to be you); if you need to, you could
get around that restriction by installing a self-signed root certificate on
your phone and then creating a SSL certificate using that.

The OpenRosa spec says that Digest Authentication is the minimal required
authentication for a client. Basic Authentication does not need to be
supported. ODK Collect supports Digest Authentication on any port, and
Basic Authentication over ports 443 and 8443 (which are the default HTTPS
ports). We'd love to support OpenID to Google, but that's a ways off.

Hope that helps.

Mitch

··· On Sat, Sep 24, 2011 at 9:48 AM, Matteo Sisti Sette < matteosistisette@gmail.com> wrote:

Now I am using https on the server, with Basic Authentication:

  • when retrieving the form list, ODK Collect crashes

  • when submitting a form I get: "FAILED: generic exception. great"

Any idea?

On 09/24/2011 06:23 PM, Matteo Sisti Sette wrote:

I'm using Basic authentication now on the server.

I have set up the server settings in ODK Collect with the username and
password; however, when I send a form, it asks me for the user and
password again. Then, after inserting them, it hangs forever at "sending
form".

By looking at the access log on the server, I see that when ODK issues
the HEAD request it gets a 401 response and then when it issues the POST
requests it gets 401 again.

Now I've tried to retrieve the form list, and it keeps asking me user
and password again and again.

So everything looks like as if i was not inserting the correct user and
password, but they ARE correct (I insert the same credentials from a
browser and they work)...... What else may I check out? I'm stuck...

On 09/24/2011 05:11 PM, Yaw Anokwa wrote:

hi matteo,

please submit a bug report or a patch if you feel what we have now
with the timeouts are not adequate.

if there are no useful debug messages when you use the logger, then i
encourage you to download the collect source and add some so you can
track down your issue.

yaw

On Sat, Sep 24, 2011 at 18:03, Matteo Sisti Sette matteosistisette@gmail.com wrote:

On 09/24/2011 04:53 PM, Yaw Anokwa wrote:

collect takes a long time to timeout because most of our users are on

unreliable connections where longer timeouts are needed. that's why
the connection seems to hang.

I see. Anyway in this case I can't see how a timeout can happen at
all. If
the server is not using the correct security or whatever, the client
should
be able to detect it and stop waiting, shouldn't it?

if you need more detailed error messages, we try to print them to the

log (run adb logcat).

I installed the Log Collector application recommended by somebody in
this
list and sent myself some logs but there's nothing apparently related
to odk
collect in there...... what am I missing?

we

don't bubble them up to the ui because "socket timeout exception"
isn't exactly user friendly.

Yes of course, I wouldn't expect such a message to be bubbled up to
the user
as is, I would just expect some error message rather than waiting
forever.

Thanks
m.

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@**googlegroups.comopendatakit%2Bunsubscribe@googlegroups.com
Options: http://groups.google.com/**group/opendatakit?hl=enhttp://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@**googlegroups.comopendatakit%2Bunsubscribe@googlegroups.com
Options: http://groups.google.com/**group/opendatakit?hl=enhttp://groups.google.com/group/opendatakit?hl=en

--
Mitch Sundt
Software Engineer


University of Washington
mitchellsundt@gmail.com

digest has worked with
our gae and local servers in 1.1.7 over http. others have built
backends against the new api that have worked,so if it's not working,
the problem is likely with your backend.

Great, that gives me some hope.

Now I've been able to set up Digest Authentication (over http) on the
server, so the server is clearly doing something different than the
client expects, but I cannot see anything conflicting with
https://bitbucket.org/javarosa/javarosa/wiki/AuthorizationAPI

Now I get the formList correctly (part of its content is not being shown
but I still have to study the new API for the formList), but when I try
to submit, I get either the "FAILED: network login?" error or it hangs
indefinitely sending.

By looking at the server access logs, I see it does two HEAD requests,
the first one gets a 401 response and the second one a 200 response, but
it never gets to do the POST request.

Here's the response from the server to a HTTP HEAD request to /submission:

HTTP Response Header
Name Value Delim
Status: HTTP/1.1 401 Authorization Required
Server: Apache/2.2.3 (CentOS)
WWW-Authenticate: Digest realm="xxx",
nonce="bbwHN7WtBAA=a6fe7e361afe51ff5a76443a93a92c0243a871a5",
algorithm=MD5, domain="/my/path/", qop="auth"
Last-Modified: Tue, 31 May 2011 16:00:20 GMT
ETag: "c54333-4be-4a49480364d00"
Accept-Ranges: bytes
Content-Length: 1214
X-Powered-By: PleskLin
Connection: close
Content-Type: text/html

··· On 09/24/2011 09:20 PM, Yaw Anokwa wrote: Date: Sat, 24 Sep 2011 19:48:50 GMT

By looking at the server access logs, I see it does two HEAD requests,
the first one gets a 401 response and the second one a 200 response, but
it never gets to do the POST request.

To be more precise:

  1. I open ODK Collect from scratch and try to send a finished form

=> it does a HTTP HEAD and gets 401, and a HTTP POST and gets a 401
(this is strange because in server settings there are the correct
username and password)

  1. it asks me to insert username and password. It offers me the ones
    that are in the settings, i leave them untouched because they are
    correct and hit OK

=> it does a HTTP HEAD and gets 401 and does ANOTHER HTTP HEAD which
gets a 200 response

=> then it stays indefinitely waiting ("Sending 1 of 1 items") forever
and never does a POST request.

Hi,

Thanks a lot for the clarifications. Indeed bugs 274 and 275 were making
even more difficult to figure out what was going wrong.

Additionally, I hadn't realised that the client expects a "204 No
content" response AND a Location header in response to the HEAD request
when the authentication is OK. I couldn't find that documented anywhere
except th source code and I think it's far from obvious (someone in the
list agreed it's a bit of an "abuse" of http, actually I find the http
specification itself to be a bit ambiguous about this).

In the meantime, I have given up https in favour of http + Digest
authentication and I got it to work.

Anyway in the mid term I am interested in this:

if you need to,
you could get around that restriction by installing a self-signed root
certificate on your phone and then creating a SSL certificate using that.

Do I need to root the device to be able to do that?

thanks for your help
m.

Matteo, I had exactly the same issues and I traced the bugs and submitted
patches for them. I'm not sure when they're going to be incorporated into
the main line. If you want to just add my patches they're on the issue
tracker. Search for tomsmyth@gmail.com

Good luck.

··· On 24 September 2011 16:24, Matteo Sisti Sette wrote:

By looking at the server access logs, I see it does two HEAD requests,

the first one gets a 401 response and the second one a 200 response, but
it never gets to do the POST request.

To be more precise:

  1. I open ODK Collect from scratch and try to send a finished form

=> it does a HTTP HEAD and gets 401, and a HTTP POST and gets a 401 (this
is strange because in server settings there are the correct username and
password)

  1. it asks me to insert username and password. It offers me the ones that
    are in the settings, i leave them untouched because they are correct and hit
    OK

=> it does a HTTP HEAD and gets 401 and does ANOTHER HTTP HEAD which gets a
200 response

=> then it stays indefinitely waiting ("Sending 1 of 1 items") forever and
never does a POST request.

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@**googlegroups.comopendatakit%2Bunsubscribe@googlegroups.com
Options: http://groups.google.com/**group/opendatakit?hl=enhttp://groups.google.com/group/opendatakit?hl=en

Oh thanks a lot!!

Did you perhaps also find out some kind of workaround? Some way of
compensating on the server side for the buggy behavior of the client?
After all, there are servers out there working against the current
version of ODK Collect...

thanks
m.

··· On 09/24/2011 11:30 PM, Thomas Smyth wrote: > Matteo, I had exactly the same issues and I traced the bugs and > submitted patches for them.