Hello, that's really odd.
So you are saying it does not show some of the content. Yet, you don't get any browser warning on console or anything?
Google Chrome often makes updates that just break it for cases it used to work a long time, that's really unfortunate, but most times there are ways to go around the problem and make it work.
Nevertheless, one important step would be to identify what exactly is the issue preventing the page to work.
Are you able to reproduce the issue if you just publish a simple Ext.NET page on your website? We would require the minimal scenario necessary to reproduce the issue before we can further understand this and help you.
I suggest you to draw a simple Ext.NET page, maybe based on an example at our examples explorers
. Maybe with little modification in a simplified example you can reproduce the issue and share that code here so we can reproduce it on our side and pinpoint the cause, suggest you a workaround for the time being and log as a bug (and fix) as it fits.
We also have some old, Ext.NET 2.x, threads where issues related to Ext.NET and SSL have been fixed.The problem is that as per your report, there's no warning/error message in the browser while loading the page, what was the cause back then.
You may want to review this forum thread to check whether your problem is possibly a regression of the one discussed in this thread: HTTPS issues with non https content
. Here, it was discussed the issue caused by some CSS files referencing non-https endpoints in given circumstances, but were fixed back in the v2 release still.
In the end, as I said in the previous post, the Ext.NET examples
runs over SSL connection and everything is showing up just fine, so we would need to know what component or setting you add to your page so that it breaks once run over SSL.
Please understand we do not want your proprietary code
, by the contrary, we need a simple
test case, preferably based on one from examples explorer, just to illustrate the scenario required to reproduce the issue. Then we could step-in the page loading process and identify the actual cause.
Here's another suggestion, if feasible: you could just clone the whole Ext.NET Examples repository
and publish it to your HTTPS website; then check if it works, or where it breaks. But that would basically only help by ensuring whether it is a project setting or IIS setting that could be affecting the website behavior over SSL.
Sorry for the long reply, tried to be the most complete and clear the possible while the provided information at this point still does not shed a light on the actual problem and possible solution.
While we are at the long read, I'd suggest you reviewing our guidelines on posting threads, there are useful tips on making simplified test cases, if this scenario can be reproduced in simple cases:
- Tips for creating simplified code samples
- More Information Required
- Forum Guidelines
Hope this helps!