Axure handwriting url blocked because its still HTTP

#1

Hi, i know you said ‘Web fonts will work with our new HTTPS architecture—but not yet.’ with the https move, but it seems axure handwriting is also still HTTP and thus being blocked:

The page at ‘https://xxx.axshare.com/…’ was loaded over HTTPS, but requested an insecure stylesheet ‘http://share.axure.com/fontCss?family=Axure%20Handwriting:r,b,bi,i’. This request has been blocked; the content must be served over HTTPS.

  • are we doing something wrong?
  • is there a workaround (a HTTPS CDN location for axure handwriting?)
  • when is a fix expected?

Its quite annoying as you can expect, as we don’t have control over our clients/target audiences pc’s and thus can’t ensure they have the font…

#2

Hi Bertus,

Sorry about this, and thanks for letting us know! We’ll file the issue with development to see how quickly we can get this cleared up. In the meantime, the best workaround is to switch the workspace containing your project back to HTTP, from HTTPS. Instructions for doing so are here: Axure Share Maintenance today (11/16/17) at 4:00-4:30 PM (PST)

Thanks,
Rachel

#3

ah, missed that setting, fixed it for now, thanks!

#4

Hi Bertus and anyone else who ran into this,

The full fix is live on Axure Share now, so you can safely return these prototypes using Axure Handwriting to HTTPS security.

Best,
Rachel

#5

thanks for the feedback!

unlisted #6