Proxyman (amazing app BTW) seems to be blocking Instagram login and feed refresh from iOS. Is there a work around for this?
Other domains are proxying just fine. If I turn of the proxy mapping on iOS Instagram works as expected.
You're unable to capture HTTPS traffic from Instagram/Facebook/... because they are using SSL Pinning. It prevents MitM apps to intercept unless you have their pinned certificate or jailbreak devices.
Related
I'm trying to switch to Firefox for development but I'm stuck at this error and I have no idea what it could be.
The problem is specifically with our Login endpoint, which sets HttpOnly cookies on successful login. In development this works on both Safari and Chrome, but trying to login on Firefox returns a NS_ERROR_DOM_BAD_URI error.
In development, web is running at http://localhost:3000, the API is on https://localhost:5001.
I assume Firefox is blocking the login because the api and the web are technically on different origins, but I don't understand why it would be doing that for localhost.
Is there a way to disable this error entirely?
I am using the Postman native app on Windows 10 and am struggling with trying to capture https requests. Postman's Documentation for this is for Mac and not Windows.
In particular, I am working on a web application that creates a session cookie upon login that needs to be included in most requests in order to be authorized. When I was using the Chrome App, Postman Interceptor achieved this (see https://stackoverflow.com/a/32436131/3816779).
Here's what I've tried so far:
Turn on the Proxy in Postman with port 5555.
Configured windows to send http and https requests through Postman's proxy server (127.0.0.1:5555).
This allows http requests to be captured in Postman
But when trying to connect to https sites, I get an error
Here are my Postman settings if that helps.
Update I ended up switching back to the Chrome App, which uses the "Interceptor" instead of a "Proxy Server" to capture traffic.
Unfortunately, capture https requests with postman native app is impossible in some case according to the official doc: Capturing HTTP requests
Note: for the Postman native apps, request captures over HTTPS will not work if the website has HSTS enabled. Most websites have this check in place.
Postman's proxy now supports HTTPS traffic - https://blog.postman.com/postmans-proxy-now-fully-supports-https-endpoints/
Once you install a CA certificate that Postman generates for your installation, capturing HTTPS requests should be seamless.
Disclaimer: I work at Postman
With Google Chrome i don't know how to fix the issue. But you can use to open the web page for example IE..
EDIT:
Or MAYBE you can start Google Chrome with parameter --ignore-certificate-errors to ignore the error message.
Postman Interceptor is available for Postman native apps which supports both features:
1. Capturing requests
2. Syncing cookies
Learn more here.
Just check HTTPS in setting and will work for you
We have a site in a S3 bucket configured to serve static HTML. The HTML app is an AngularJS app. The AngularJS app requests its data with ajax through HTTPS with a self signed certificate to our backend API. All the GET requests work fine, but when we POST,PUT or DELETE in chrome the ajax requests get canceled.
All types of requests works in Firefox.
Our solution has been to disable HTTPS but that does not seem like a long term solution. Bought certificates is not an option for us.
We have noticed that the requests works in some versions of chrome. Is this something normal in chrome? Is there any way to avoid this?
Thanks for any kind of answer that might help us!
Yes Tyler! You are right! Chromes very much dislikes certificates that is not signed by a trusted authority.
Im doing a web based mobile application. uses tomcat as well. when i edit the tomcat to use https for my front end application basically all the jsp and servlets, it totally lags in mobile browser suchs as android. In iphone safari, it is worse, server connection error.
f.y.i, http works fine and fast.
Does anyone has any experience in this? does the certificate plays a part in the lagging?
Try to use online tools to make sure nothing is wrong with your certificate. example DigiCert.
Also check in your browser if there is a problem with the certificate (Chrome makes easy to check this, click on the secure icon at the left of the URL).
If all I said above is file I think the problem is from your HTTP server configuration.
Are you using port 443 and did you change default values?
When I am calling a REST service through AJAX, its working fine. I am calling it with the URL staring with HTTP e.g.: http://www.myserver.com/customers. Its works really great.
But when I am calling a same URL but with HTTPs e.g.: https://www.myserver.com/customers,
I am not getting any response from server.
Its not working for GET or POST both.
Its not working in Mac firefox, actually I am developing an application for iPhone using phonegap framework.
Its also not working in iPhone simulator's mobile safari.
Can anyone here know what problem is this? And how to solve this?
The requesting domain must match the requested domain down to the protocol, according to the Same Origin Policy
It could probably be because of same origin policy. read
http://en.wikipedia.org/wiki/Same_origin_policy