This is weird. I created a Facebook iFrame App that worked fine in every browser I've tested it on. Then Mountain Lion came out. For some reason macs running the new OS and Safari 6 can't see the app. The Facebook chrome is there, but the website isn't loading. (The app is just a website hosted elsewhere). I have another mac running lion that has Safari 6, but it works fine. So it has to be Mountain Lion that's causing this problem. I don't see how the operation system would affect this, but it seems to be.
Any suggestions?
No matter what browser I am using, the address https://www.yellow-mountain.com/latest_picture/ is not reachable (my browsers try to connect to the HTTPS version because I am browsing FB over HTTPS). And even outside any iframes I can not connect to that address.
Reaching it just via HTTP works fine though.
So talk to your server admin about getting SSL to work for your server/domain.
Try to clear the browser's cache. It works pretty well for me.
Related
With device manual proxy to my Charles IP address, not seeing any traffic or prompt to allow traffic in Charles Proxy. S10 device appears to load all traffic when navigating to various URLs.
Even charlesproxy.com/ssl loads website but doesn't initiate a certificate to download.
All other android devices tested on same setup works fine. Issue seems specific to Samsung S10
So what seemed to have worked for me just now, with my mac (I assume it would be something similar for Windows) I just opened a regular browser, went to chls.pro/ssl and download the certificate file.
From there I sent it to my S10+ and opened it, which then installed it properly.
If you're trying to hook up to Android devices then beware that Google introduced security measures to not allow proxy monitoring in I believe Android 6 or 7. If the other devices you had worked fine on Android then it's probably because you were using an earlier version of Android, or, you had a debug build that allowed for proxy monitoring. I know there's a SO post somewhere that talks about this "pinning" and I know our company does this as well with debug apk's. If neither of those solutions work then it's probably a matter of getting the Charles certificate installed correctly on that phone but without more information it is hard to diagnose. Hope this helps you
I have integrated facebook and gmail in my app but when i redirect user to safari for login i am not able to open facebook or google page for loginin safari in simulator. it gives me error like "safari can not open the page because it can not establish secure connection to the server."
Any one knows what is solution to resolve this issue?
Thanks in advance.
Below are common issues in such cases
Disable 'Auto Proxy discovery' in proxy settings of your Mac
You are behind a proxy
You are using a Antivirus which has WebShield of similar feature enabled. Disable the antivirus and try again
Your simulator's date & time are not sync to current date. Certificates don't validate fine when system date is skewed
Rebooting the simulator also at times help
Below are the threads you should look into
Can't visit website on iOS Simulator—'This Connection Is Not Private'
iOS simulator can't access any URL and shows the error "This connection is not private"
iOS Simulator not works on https, all https are evaluated as not trusted
Can't use HTTP in iOS 8 simulator
iPhone simulator cannot connect to internet
I fixed this by disabling Avast Web Shield.
I have Avast Antivirus installed and adding facebook url to the configuration of the internet scanning service allowed me to fix this problem.
I have installed MAMP V 3.5 today on Macbook Air, OS X El Capital, V 10.11.2 When I launch the application, the Server shows it is connected to Apache, but the web browser (Safari V.9) fails to open the page. the URL reads
http://localhost/MAMP/?language=English
Safari doesn't work for me, even though it's my browser of choice.
Try Chrome, and make sure you type: localhost:8888/
(or whatever port number you choose, if not the default)
Hope that helps.
Tyler
I'm trying to run some local testing on iDevices but I must be missing something in the setup. I did that before when it all worked, so maybe someone can helpout:
I'm using Fiddler on a windows machine, have all devices set up via proxies and yes it also captures the traffic of the iphone and ipad.
I've got a few localhost vhosts set up, so running
http://mydomain.local
this works swimmingly on the windows phone via proxy to fiddler. but the iphone and ipad just says the server stopped responding.
The firewall is completely turned off and I can see all other traffic from the iDevices, so what could be the issue? Why does the iphone not read the hosts file but the windows phone does?
Almost a year late, but I had the same problem and can confirm that iOS does reserve ".local" to identify Bonjour-accessible devices
If possible just change your domain extension to something else like ".lan" and your requests will go through the Fiddler proxy as expected.
I am building a .NET website with MonoDevelop on OSX Lion that is targeted for mobile devices.
On my desktop's browser, I am able to access the site via http://127.0.0.1:8080, but I would like to view it on my physical iPhone (I don't want to use the XCode simulator).
My iPhone and Mac are on the same network and I have enabled Web Sharing. I can actually get to the default Apache index.html (http://192.168.1.104:80) page, but I am not able to get to my site (http://192.168.1.104:8080).
I'm newer to the Mac and even less familiar with network management, so I hope I'm missing something very simple.
You may as well turn off web-sharing because web-sharing only operates the built-in Apache web-server.
What is happening is that the web-server that MonoDevelop is hosting your pages on has been set up to only allow connections coming from localhost. If this is the problem, entering in the lan IP of the OS X machine on the OS X machine will likely also not work (if the IP filtering work like it does on Apache).
You need to find the config files for the MonoDevelop server and allow access from addresses other than 127.0.0.1