FontLab Forum
2012-05-21, 01:22:52 *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to the FontLab forum, read how to use it! Update: Archives from old MSN forums are now available on our forum.
 
   Home   Help Search Calendar Downloads Tags Login Register  
Del.icio.us Digg FURL FaceBook Stumble Upon Reddit SlashDot

Pages: [1]
  Print  
Author Topic: Fonts won't stream under HTTPS/SSL  (Read 1280 times)
ArchivePoster
Guest
« on: 2000-07-16, 18:20:00 »

Posted by: alexfry
         

Logged
ArchivePoster
Guest
« Reply #1 on: 2000-07-16, 20:14:00 »

Posted by: Si
         

Do you have an online example we can all take a look at?

Si


Logged
ArchivePoster
Guest
« Reply #2 on: 2000-07-16, 21:31:00 »

Posted by: alexfry
         

Thanks for the swift response - I've made some headway on the problem that would indicate a lack of understanding on my part....unfortunately the URL isn't a public one at the moment but I may be able to open it up if we can't resolve the problem.

I can get it working if I add all of the potential domains/pages as follows:

https://10.1.1.219
https://10.1.1.219/
https://10.1.1.219/index.asp
https://10.1.1.219:443
https://10.1.1.219:443/
https://10.1.1.219:443/index.asp

However, I'm unsure which of these is the one that works and for which cases - also, if there is any sort of query string on the end, eg.

https://10.1.1.219/index.asp?page=display

then it bums out again - I've seen the Advanced option for declaring script calls, but can't believe I have to include them all !!??  Similarly, I don't really want to harvest all of the page names using the WEFT tool as the site will be changing regularly.

Any advice/assurance about more generic configurations would be very welcome.

Cheers

Alex


Logged
ArchivePoster
Guest
« Reply #3 on: 2000-07-17, 10:38:00 »

Posted by: mjan
         

The bind urls that you specify needs to match the url used in browsers when viewing the pages. The browser verifies this rule literally by checking that a page begins with one of the allowed urls. This is a restriction on where the pages are, not where the eots are (the eot may even be located anywhere, and accessed with any protocol).

For examples:
bind url: https://www.mycorp.com/ 
allowed page: https://www.mycorp.com/index.asp
allowed page: https://www.mycorp.com/index.asp?page=foo
not allowed: http://www.mycorp.com/index.asp    Wrong protocol.
not allowed: http://10.1.1.219:443/index.asp   Wrong host.

WEFT Development,
- Michael


Logged
Tags:
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!