Story and sources behind httpclientandroidlib-4.2.1.jar?

Dear ODK Team,

On August 16, 2012, Collect began using a custom-built Apache HTTP library:

https://code.google.com/p/opendatakit/source/detail?r=a764da00557f57ef5ba6873d966142dd5edf0e6b&name=v1.2.2%20rev%201023&repo=collect&path=/lib/httpclientandroidlib-4.2.1.jar

But we can't find the sources anywhere.

The reason we're looking is this: we're trying to build a version of
Collect managed by MobileIron's mobile device management solution which,
among other things, intercepts HTTP traffic for tunneling. MobileIron's
solution fully supports the Apache library, but it's not working for
Collect -- we suspect because it's not intercepting calls made through this
custom build.

Can anybody tell us more about this custom build and why it's necessary?
And/or share the sources? We're tempted to swap it back out for a stock
Apache library, but obviously we'll run into whatever trouble provoked the
switch in 2012.

Thanks very much,

Chris

Upon further investigation, it looks like this:

https://code.google.com/p/httpclientandroidlib/

Was used to add a LogFactory here:

https://code.google.com/r/mitchellsundt-logfactory/

We're investigating shifting to this instead:

https://hc.apache.org/httpcomponents-client-4.3.x/android-port.html

But it looks like that will take some work. One way or another, it seems
like we might need to get to a standard Apache API in order to support
MDM/tunneling. Any advice more than welcome.

Thanks,

Chris

··· On Wed, Jun 11, 2014 at 9:17 AM, Christopher Robert wrote:

Dear ODK Team,

On August 16, 2012, Collect began using a custom-built Apache HTTP library:

https://code.google.com/p/opendatakit/source/detail?r=a764da00557f57ef5ba6873d966142dd5edf0e6b&name=v1.2.2%20rev%201023&repo=collect&path=/lib/httpclientandroidlib-4.2.1.jar

But we can't find the sources anywhere.

The reason we're looking is this: we're trying to build a version of
Collect managed by MobileIron's mobile device management solution which,
among other things, intercepts HTTP traffic for tunneling. MobileIron's
solution fully supports the Apache library, but it's not working for
Collect -- we suspect because it's not intercepting calls made through this
custom build.

Can anybody tell us more about this custom build and why it's necessary?
And/or share the sources? We're tempted to swap it back out for a stock
Apache library, but obviously we'll run into whatever trouble provoked the
switch in 2012.

Thanks very much,

Chris

Glad Apache has stepped up to provide this. That would be great to move
onto.

The update was originally to move off of the 4.0-pre image to one that
better supported authentication protocols and cookie management. There were
also a number of security fixes in the DigestAuth implementation that made
sense to upgrade to include.

Mitch

··· On Wed, Jun 11, 2014 at 8:07 AM, Christopher Robert wrote:

Upon further investigation, it looks like this:

https://code.google.com/p/httpclientandroidlib/

Was used to add a LogFactory here:

https://code.google.com/r/mitchellsundt-logfactory/

We're investigating shifting to this instead:

https://hc.apache.org/httpcomponents-client-4.3.x/android-port.html

But it looks like that will take some work. One way or another, it seems
like we might need to get to a standard Apache API in order to support
MDM/tunneling. Any advice more than welcome.

Thanks,

Chris

On Wed, Jun 11, 2014 at 9:17 AM, Christopher Robert <crobert@surveycto.com wrote:

Dear ODK Team,

On August 16, 2012, Collect began using a custom-built Apache HTTP
library:

https://code.google.com/p/opendatakit/source/detail?r=a764da00557f57ef5ba6873d966142dd5edf0e6b&name=v1.2.2%20rev%201023&repo=collect&path=/lib/httpclientandroidlib-4.2.1.jar

But we can't find the sources anywhere.

The reason we're looking is this: we're trying to build a version of
Collect managed by MobileIron's mobile device management solution which,
among other things, intercepts HTTP traffic for tunneling. MobileIron's
solution fully supports the Apache library, but it's not working for
Collect -- we suspect because it's not intercepting calls made through this
custom build.

Can anybody tell us more about this custom build and why it's necessary?
And/or share the sources? We're tempted to swap it back out for a stock
Apache library, but obviously we'll run into whatever trouble provoked the
switch in 2012.

Thanks very much,

Chris

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

Thanks, Mitch, for the reply.

We've swapped out to use the Apache Http 4.3.3 library, and we're testing
now. So far so good. We'll flag this to contribute back to core once we're
sure it's working well.

Thanks again,

Chris

··· On Wed, Jun 11, 2014 at 4:41 PM, Mitch Sundt wrote:

Glad Apache has stepped up to provide this. That would be great to move
onto.

The update was originally to move off of the 4.0-pre image to one that
better supported authentication protocols and cookie management. There were
also a number of security fixes in the DigestAuth implementation that made
sense to upgrade to include.

Mitch

On Wed, Jun 11, 2014 at 8:07 AM, Christopher Robert <crobert@surveycto.com wrote:

Upon further investigation, it looks like this:

https://code.google.com/p/httpclientandroidlib/

Was used to add a LogFactory here:

https://code.google.com/r/mitchellsundt-logfactory/

We're investigating shifting to this instead:

https://hc.apache.org/httpcomponents-client-4.3.x/android-port.html

But it looks like that will take some work. One way or another, it seems
like we might need to get to a standard Apache API in order to support
MDM/tunneling. Any advice more than welcome.

Thanks,

Chris

On Wed, Jun 11, 2014 at 9:17 AM, Christopher Robert < crobert@surveycto.com> wrote:

Dear ODK Team,

On August 16, 2012, Collect began using a custom-built Apache HTTP
library:

https://code.google.com/p/opendatakit/source/detail?r=a764da00557f57ef5ba6873d966142dd5edf0e6b&name=v1.2.2%20rev%201023&repo=collect&path=/lib/httpclientandroidlib-4.2.1.jar

But we can't find the sources anywhere.

The reason we're looking is this: we're trying to build a version of
Collect managed by MobileIron's mobile device management solution which,
among other things, intercepts HTTP traffic for tunneling. MobileIron's
solution fully supports the Apache library, but it's not working for
Collect -- we suspect because it's not intercepting calls made through this
custom build.

Can anybody tell us more about this custom build and why it's necessary?
And/or share the sources? We're tempted to swap it back out for a stock
Apache library, but obviously we'll run into whatever trouble provoked the
switch in 2012.

Thanks very much,

Chris

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.