I'm working on an ASP.NET MVC5 app, upgraded from MVC3, to 4, and now to 5.
I deployed it to an internal IIS 7.5 server that has a wildcard cert on it. The CA is an enterprise trusted root by domain group policy.
When I load my site, I'm expecting a nice green lock icon in Google Chrome, but instead I get:
In the Chrome developer tools, on the Network screen, I'm looking at all the resources that were collected by the browser. Each one is going over HTTPS.
Why am I getting this error?
Well, it looks like something weird happened in Chrome. I shut down all my browser windows, and when I started the site back up again, all was well and I got my green lock icon.
Related
We have an iOS app that has a Watch Tutorial link to our website. We recently migrated our website and the page it points to is now showing a 404 error. We need to know what page the link points to so we can redirect it. Unfortunately in the app it just opens link to the page in the actual app and not in safari or any other browser so we can't see the website link.
Is there a way to "inspect" the link in our app like you can in a browser to see where it is pointed to? Maybe some debugging software that can pull the app down and let me look at it? Our app developers are unavailable right now and we want to get the app up and running correctly.
You can try with the Safari Web Inspector (Safari mac remotely debugging on an iPhone app/safari).
With this approach, you can inspect from you mac, any WebViews (or related) in actual apps.
Note : It won't work if you app make the request, but does not use web view to display the page.
See any tutorial on how to enable safari web inspector
Maybe some debugging software that can pull the app down and let me look at it?
You can use a web proxy such as Charles to easily see all the traffic going to and from the app:
Install the proxy software on your computer.
Set the device to proxy through your computer.
If needed, install SSL certificates that will let the proxy see the contents of TLS connections.
Fire up the proxy, launch the app, and watch the traffic.
I am using the the HTML5 Video tag on a PWA created in angular 6 and for the life of me I can't get it to work. At first I thought it was an issue with encoding since it works on FF, Chrome (Desktop and Mobile), and Safari Desktop. I have checked the encoding and the use of the video tag. I believe that all is in order. I am able to play the video on iOS when serving it using HTTP from my local.
ng serve --host 0.0.0.0
It fails to play when trying to use HTTPS and a cert generated from openssl.
http-server dist/marcel-webapp/ -S
This leads me to believe that the issue is only with untrusted certificates. The problem that I having a very hard time finding the solution to is that I am hosting it on Firebase, and google handles the provisioning of the SSL certificates automatically. I checked my version of the trust store on my phone and the neither the root or intermediate certificates in use are listed.
Here is the link to the video my site
The question is... If really do have a certificate issue on firebase, what can be do about it?
Thanks in advance for any guidance on this.
Update and actual problem identified! I eliminated an untrusted certificate as the problem by deploying to AWS. The problem is actually related to the service worker created when adding PWA support to the project. The reason the video works over HTTP is that service workers are only enabled in HTTPS. I'm using Angular 6 to create the PWA, however it seems that other frameworks have the same problem. Turning off services workers in the Safari allows the video to display as expected
Settings > Safari > Advanced > Experimental Features > Service Workers
I found this post describes the problem in great detail. View Post Here
I have a weird situation, I am developing a site I can see all of the images well on my mac as well as an android phone but on my iPhone and my friends mac, and iPad it is not displaying the images when using safari. Is there something I need to add to the files for this to display properly all through out?
Thanks all feedback welcomes
It appears these assets are linked using https but there is not a valid SSL on the site. So on the devices where it works you have either authorized the SSL or bypassed it, but the other devices have not.
If you open up the Developer Tools in Chrome and view the console you can see the assets with issues along with the error message... "Failed to load resource: net::ERR_INSECURE_RESPONSE"
Just in case someone else has the same problem. For me the problem was that a plugin "Ewww image optimizer" converted images to webP, these were then cached and served by cloudflare and wouldn't load in safari
I have https server configured with ssl options.I configured certificates in Settings>General>Profiles.
When I access my server using Safari browser it works fine. But same doesn't work with Firefox,chrome and my ios app.
Do I need to do any specific step to solve this problem?
I am afraid it is not possible to solve this issue :/
I'm having the exact same problem: I have installed a custom certificate on my IPad and the secure connection works fine on Safari, but on Firefox the website tells me that there is no certificate installed
On the desktop application there is an option to add certificates to Firefox (tools > security > certificates), but this option does not exists in Firefox
From my understanding this is due to Firefox for IOS having only very limited functionalities (no module for example), so unfortunately it looks like it is not possible to set Firefox for IOS to use local security certificates...
I am using MVC4 mobile display mode.
It works perfectly locally - if I use a user agent switcher it switches to mobile as expected.
As soon as I deploy it to my live IIS server it doesn't ever go to the mobile view on a phone or with user agent switched.
The server has .Net 4.5 on it and the site is using .Net 4 integrated for its app pool. (So doesn't seem to be this ASP.NET MVC4 mobile site displays correctly on local host not deployment server)
Any other ideas?
If anyone else has this issue make sure you check that the view is being deployed to the live server. It wasn't marked as Content for me so wasn't being dployed. I guess because I copied it into the project.
Anyway simple error on my part.