6 Aug 2012 1:32 PM #1
Unanswered: Native features (Camera/Msg Boxes/etc.) behind a proxy server
I connect my iPad to our corporate wireless access point, but must use a proxy to get to the internet. I have found that when we connect via the proxy, that the Camera and other Native Features do not function. I see that in Ext.device.communicator.Default that it tries to connect to http://localhost:3000'. The iPad does not have a proxy bypass that I'm aware of, and therefore even localhost gets routed through the proxy server which promptly denies that request.
Is there any way to get Sencha to bypass the proxy server for localhost?
I'm sure others may be experiencing the same issue, but are unaware their proxy server is getting in the way.
8 Aug 2012 5:34 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services firstname.lastname@example.org
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
8 Aug 2012 7:19 AM #3
The requires for camera and other native features are included in my build, and I can get the camera and other native features to work just fine, provided I'm not connected through our proxy server.
Here's why it matters...
In our office, our wireless access point has no direct internet or intranet access. We must point to our proxy to get internet access. So in order to test my app, I must be connected to our proxy to connect to our host servers. Once I do this, I no longer have access to the iPad native features.
If I turn off the proxy, I can operate the camera and native message boxes no problem. But then of course, I don't have internet access, and my app can't talk to my host servers.
You can easily try this on your own ios device with a barebones native app. Specify a proxy on your ios device. Even if you don't have one, just make up an address ex:10.0.0.1. Now none of your native functions will work.
I really feel this is a bug in ios. They should never route localhost/127.0.0.1 to the proxy server in the first place. Or at least provide a bypass proxy list.
Maybe you have some ideas on how to get around this?