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 mailto:tomsmyth@gmail.com
I've downloaded the ODK Collect source code and I've been able to build
it and it works (with the same bug as before, of course).
So I'm trying to apply your patch. I'm absolutely new to patching. I get
this message when I try to apply your patch for issue #274:
Does this mean that the patch has already been applied into the version
of the source code that I've downloaded? (if so, then it means it
doesn't solve the issue, unless your patch for 275 does)
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)
2. 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 <mailto:opendatakit@googlegroups.com>
Unsubscribe: opendatakit+unsubscribe@__googlegroups.com
<mailto:opendatakit%2Bunsubscribe@googlegroups.com>
Options: http://groups.google.com/__group/opendatakit?hl=en
<http://groups.google.com/group/opendatakit?hl=en>
The Location header is used to detect wifi network login screens (e.g.,
Starbucks') which would otherwise return 200 in response to a /formList
request. It is perhaps an odd use of the header, as it is not a "new
location" but just a confirmation that you've hit the location you
intended.
Location was required for ODK Collect 1.1.5 and earlier - they checked a
prefix match, which is why "http" was a valid reply; we continued to use it
in ODK Collect 1.1.7 for this same purpose but now also check that the
server URL matches. That might be overkill.
W.r.t. certificates, I don't know. Another option is to figure out how to
set up an HttpClient so that you can add your own root certificates in
addition to the ones supplied by the phone manufacturer.
Mitch
···
On Tue, Sep 27, 2011 at 11:00 AM, Matteo Sisti Sette < matteosistisette@gmail.com> wrote:
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?
has a bunch of options that work on non-rooted phones.
yaw
···
On Tue, Sep 27, 2011 at 21:00, Matteo Sisti Sette wrote:
>> 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?
>
While this is an interesting discussion it is more appropriate to have
on the ODK developer list.
As a reminder of what each list is for:
ODK Community – our main list for discussing any issue relevant to
the entire community
ODK Developers – for people who contribute new code and/or change
existing code
Keep the discussion going, just on the appropriate email lists. This
is a code centric discussion which means it probably belongs on the
developer list. We want to maintain a list that community members who
are not programmers can follow the discussions on.
Waylon
···
On Sat, Sep 24, 2011 at 2:53 PM, Matteo Sisti Sette wrote:
> 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.
>
> Hi,
>
> I've found these issues but none of them corresponds exactly with the one
> I'm experiencing:
>
> http://code.google.com/p/opendatakit/issues/detail?id=274&q=tomsmyth
> http://code.google.com/p/opendatakit/issues/detail?id=275&q=tomsmyth
>
> According to the first issue, the uploading screen stays forever but the
> form does upload, while in my case it doesn't.
>
> According to the second issue, you ubserve "3 POST requests. One just as the
> auth dialog is appearing, and two after the credentials are entered."
>
> In my case I observe a HEAD and a POST _before_ entering the credentials,
> and two HEAD but no post at all after entering the credentials.....
>
>
> Do you think that your patch will fix my issue as well?
>
> thanks
> m.
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
Keep the discussion going, just on the appropriate email lists. This
is a code centric discussion which means it probably belongs on the
developer list.
Hi, I'd be glad to, but I can't seem to post to the developer group.
I've joined the group, but when I go to the google group page there's no
"new post" button... maybe I need to be invited or something?
Keep in mind that the tip of the development branch will typically have
changes applied to it that were not in the most recently released 1.1.7
RC1.
You may be seeing the changes already in the tip, but that is likely not
what is built and available in the APK for download.
Mitch
···
On Sun, Sep 25, 2011 at 9:44 AM, Matteo Sisti Sette < matteosistisette@gmail.com> wrote:
Hi,
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. 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 mailto:tomsmyth@gmail.com
I've downloaded the ODK Collect source code and I've been able to build it
and it works (with the same bug as before, of course).
So I'm trying to apply your patch. I'm absolutely new to patching. I get
this message when I try to apply your patch for issue #274:
Does this mean that the patch has already been applied into the version of
the source code that I've downloaded? (if so, then it means it doesn't solve
the issue, unless your patch for 275 does)
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:
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)
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.
Keep the discussion going, just on the appropriate email lists. This
is a code centric discussion which means it probably belongs on the
developer list.
Hi, I'd be glad to, but I can't seem to post to the developer group. I've
joined the group, but when I go to the google group page there's no "new
post" button... maybe I need to be invited or something?
--
If we keep uppermost in our minds the unkind and unjust acts of others, we
shall find it impossible to love them as Christ has loved us; but if our
thoughts dwell upon the wondrous love and pity of Christ for us, the same
spirit will flow out to others.
Thanks for the tip (couldn't resist it) - well, for the clarification,
but indeed, it seems that in this case the patch actually was reversed
(and was not already included in the source I had downloaded). I applied
it with -R and it worked (AND looking at the code, it does make sense).
thanks
m.
···
On 09/27/2011 07:33 PM, Mitch Sundt wrote:
> Keep in mind that the tip of the development branch will typically have
> changes applied to it that were not in the most recently released 1.1.7
> RC1.
> You may be seeing the changes already in the tip, but that is likely not
> what is built and available in the APK for download.