Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...HTTP/2 protocol and DNNHTTP/2 protocol and DNN
Previous
 
Next
New Post
4/15/2016 3:03 AM
 

Now that Windows 10 has HTTP/2 support with IIS, I have decided to play with it.  It seems ideal to serve SPA modules over HTTP/2.  There is no longer a need to concatenate javascript files anymore by utilizing a javascript module loader like SystemJS.  It is more efficient to load on demand and cache reusable resources in finer grained chunks.  Bundling was only advantageous over HTTP/1.1 because of the large cost of opening up too many TCP requests, which HTTP/2 now circumvents.

I have discovered that IIS can only serve HTTP/2 requests through TLS, and thus DNN portals wishing to take advantage of the new protocol must be browsed to via HTTPS.  There seems to be a bunch of blocked resources on a clean install of DNN8 when browsed to over HTTPS.  They look to be a bunch of font files from jquery.js and Telerik.Web.UI.WebResource.axd.  See below for logs from Chrome's console.

These 'Mixed Content' errors appear even on an empty page with no modules.  I checked the CDN settings and they are all disabled.  Would anyone happen to know how to remedy this?  Missing font resources are unlikely to break anything critical.  But it is rather obnoxious to have all these errors flooding the browser console.  There are 12 of them!


jquery.js?cdv=39:5717 Mixed Content: The page at 'https://dnndev.me/' was loaded over HTTPS, but requested an insecure font 'http://fonts.gstatic.com/s/opensans/v10/DXI1ORHCpsQm3Vp6mXoaTegdm0LZdjqr5-oayXSOefg.woff2'. This request has been blocked; the content must be served over HTTPS.

Telerik.Web.UI.WebResource.axd?_TSM_HiddenField_=ScriptManager_TSM&compress=1&_TSM_CombinedScripts_…:1135 Mixed Content: The page at 'https://dnndev.me/' was loaded over HTTPS, but requested an insecure font 'http://fonts.gstatic.com/s/opensans/v10/DXI1ORHCpsQm3Vp6mXoaTegdm0LZdjqr5-oayXSOefg.woff2'. This request has been blocked; the content must be served over HTTPS.
 
New Post
4/15/2016 5:14 AM
 
which DNN version are you running?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/15/2016 3:02 PM
 

I was using a clean install of DNN 8.0.1.  Seeing these errors on an empty page, using the default skin.  It is not too difficult to replicate.

On Windows 10, within IIS.  Simply create a self-signed certificate and add a new binding to a DNN8 website using the HTTPS type.  IIS on Windows 10 will automatically serve the site over HTTP/2 when browsed to via https:// URL.  Fortunately, there is no other configuration needed.  It just works ^_^



 
New Post
6/15/2016 1:19 PM
 
Has anyone figured this out? I have a site using DNN 8 with a trusted cert that is giving security errors in Chrome. The pages seem to work, but makes my client jittery that things aren't secure. All the exceptions point to http://fonts.gstatic.com and chrome complains it should be https:// thus creating mixed security.
 
New Post
6/26/2016 6:17 AM
 
So change it to https.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...HTTP/2 protocol and DNNHTTP/2 protocol and DNN


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out