Forum Discussion

miikka's avatar
miikka
Maven
9 years ago

SDK and HTTPS

Hi,

is anybody using the SDK with a stage running on HTTPS?

 

I upgraded to the v. 1.2.1 of the SDK and tried configuring the local CSS instance to be served over HTTPS instead of HTTP. But even if I put HTTPS in responsive.conf.json, the server always seems to start over HTTP.

 

This obviously triggers a warning in the browser and when you allow the insecure content to be shown, the page looks mostly okay. But when taking a closer look I can see that some font files are triggering errors like this:

GET http://localhost:9000/html/assets/fonts/fontawesome-webfont.woff2?v=4.3.0

And I can see that the elements using FontAwesome are broken. There's also a good bunch of warnings of insecure content obviously but those assets seem to be loaded still.

 

Any pointers would be welcome.

 

Cheers,

.M

 

  • YuriK's avatar
    YuriK
    Khoros Expert
    9 years ago

    Hey Mikka,

     

    We don't currently have a solution that we've fully tested for this use case. However I think either of the following should work.

     

    • Set up a proxy that will allow https and will (either haproxy, apache, or any other proxy), then point your community to the port where the proxy is set up (this can be done in Studio->Advanced->SDK)
    • Switch the browser to allow mixed content (you will have to search for the right way to do this in your browser)

     

    We are looking into making enhancements to this in the future, however currently the above should be a workaround.

     

    Let me know if either of the above solutions work for you.

     

    Hope this helps,

     

    Yuri

      • miikka's avatar
        miikka
        Maven
        9 years ago

        Hi YuriK,

        I tested both options and was still getting the same errors about some assets not being loaded. And then I realized that the missing assets are not included when exporting the Studio plugin from stage, for example:

        http://localhost:9000/html/assets/fonts/fontawesome-webfont.ttf?v=4.3.0 Failed to load resource: the server responded with a status of 404 (Not Found)

        As there's no /fonts folder under /assets and it looks like these are coming from the platform definitions:

        coreplugin/res/feature/responsivebase/v1.8-lia16.3/res/skins/bootstrap_base/sass/_variables.scss:877://$fa-font-path:        '/html/assets/fonts';
coreplugin/res/feature/responsivebase/v1.8-lia16.3/res/skins/bootstrap_base/sass/codebook/_variables-base.scss:956:$fa-font-path:        '/html/assets/fonts' !default;
coreplugin/res/feature/responsivepeak/v1.8-lia16.3/res/skins/responsive_peak/sass/_variables.scss:1445://$fa-font-path:        '/html/assets/fonts';

        Some configuration issue maybe?

         

        Cheers,

        .M