search

newtonandebe / opendatakit

Automatically exported from code.google.com/p/opendatakit
0 stars 0 forks source link

odk collect upload behind a proxy server #16

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Can we get ODK Collect to work in WiFi connections where a proxy server is 
present? I noticed that the presence of a proxy server prevents the app from 
uploading the file/form.

Original issue reported on code.google.com by yanokwa on 29 Apr 2010 at 10:11

GoogleCodeExporter commented 9 years ago

Original comment by yanokwa on 23 Jul 2010 at 8:19

GoogleCodeExporter commented 9 years ago

Original comment by wbrune...@gmail.com on 7 Jun 2011 at 11:19

GoogleCodeExporter commented 9 years ago

Original comment by yanokwa on 25 May 2012 at 3:46

GoogleCodeExporter commented 9 years ago

Original comment by yanokwa on 25 May 2012 at 6:40

GoogleCodeExporter commented 9 years ago 
By proxy server, I assume you mean the wifi network login server at, e.g., 
Starbucks.  The solution is to first connect using the phone's Browser, to 
negotiate any wifi login screens.  Then use ODK Collect.

Proxy servers are problematic because they often have login screens that would 
need a full web browser to see and respond to (e.g., captcha images).  Once the 
device is logged into the wifi access point, any app (e.g., ODK Collect) can 
use the wireless connection.

Original comment by mitchellsundt@gmail.com on 28 Jun 2012 at 10:42

GoogleCodeExporter commented 9 years ago 
Hi, i have tried to use odk collect with my company phone and it did'nt work on 
the mobile  internet (GPRS/UMTS/HSDPA). When i switched to wifi it did. This is 
because of our company's proxy. ODK Collect has an issue there.

Original comment by T.van_Zo...@nedtrain.nl on 18 Jul 2012 at 8:48

GoogleCodeExporter commented 9 years ago 
I'm not understanding your situation; I think it is an issue with how you set 
up your server.  

If you are using GPRS, as long as the server is visible from the internet, you 
should be able to reach it (e.g., you should be able to reach 
opendatakit.appspot.com using GPRS).  If you can't, then it is an issue with 
ODK Aggregate visibility -- see 
http://opendatakit.org/use/aggregate/tomcat-install/ for working though making 
our ODK Aggregate server visible.

If it works through wifi, then it just means that your ODK Aggregate server is 
known only through your local network connections.

The normal case for a proxy being a problem is the WiFi access point proxy, 
which requests a network login.

Original comment by mitchellsundt@gmail.com on 18 Jul 2012 at 8:55

GoogleCodeExporter commented 9 years ago 
I can think of a situation where I had the same problem and the culprit was 
Squid!. This is not an ODK issue per say, I presume one has to add some type of 
proxy "Method" to allow submissions via a squid or other proxy. My solution was 
to bypass the proxy for the aggregate URL but you would need to get your 
network engineers involved here.

Original comment by ad...@osilab.net on 27 Nov 2012 at 10:34

GoogleCodeExporter commented 9 years ago 
We are having an SSL Hostname verification issue by having our ODK Aggregate 
server behind our _reverse_ proxy. I am not sure if the original reporter is 
referring to a forward proxy like squid or a reverse proxy like apache 
mod_proxy, nginx, etc. If the former, I'll edit this comment and open a new 
issue.

For some very odd reason ODK Collect seems to be using reverse DNS in the 
process of verifying the hostname in the certificate. The specific error I am 
seeing is "Form listing failed. Error: javax.net.ssl.SSLException: hostname in 
certificate didn't match: <{fqdn matching cert CN}>!=<{some other random fqdn 
also being rev. proxied by the same host}> while accessing https://{first FQDN 
from above}/ODKAggregate/formList

Original comment by jesse.pr...@gmail.com on 20 Mar 2014 at 9:38

GoogleCodeExporter commented 9 years ago 
Can you access it via the browser on the phone?

Note that the protocols use HEAD, GET and POST requests. Not sure if you need 
to configure the proxy to support HEAD requests....

Original comment by mitchellsundt@gmail.com on 20 Mar 2014 at 10:33

GoogleCodeExporter commented 9 years ago 
My issue may have been due to using a certificate that was issued from my own 
corporate CA. I'm having other proxy issues but I will mention them in a more 
appropriate place.

Original comment by teh_g...@yahoo.com on 31 Mar 2014 at 6:54