Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Hardy Wang 91 posts 112 karma points
    Feb 29, 2012 @ 21:14
    Hardy Wang
    0

    Courier License and Domain Name Question

    I read from http://our.umbraco.org/forum/umbraco-pro/courier/22900-License-Question and I am pretty clear we can use one license for one top level domain.

    But in my company the situation is a bit unique. We have WebSEAL before our web site as reverse proxy, all the domain name resolve happens there. For all backend servers (behind WebSEAL) there is no concept of domain name at all, our WebSEAL won't pass host name to backend servers, all backend servers work with IP address only.

    In this case if we purchase Courier license with top level domain of my-company.com does it still work?

    How does Courier decide if the license matches with domain? It is done by reading server variable or it is done by reading URL/querystring in browser?

  • Per Ploug 865 posts 3491 karma points MVP admin
    Mar 05, 2012 @ 10:34
    Per Ploug
    0

    Hi hardy

    Courier licensing detects usage in 2 ways

    1. the url that the browser is using to browse the current install, so it does not care about the server config, only httpheader. So the site responds to url.com then thats all that matters to the licensing

    2. it checks when you connect to remote repos if their urls are covered by a license. this happens in the same way. A request is sent with a specific hostname on it. And the license checks this request when its received.

    So atleast in theory it should not care if its DNS, hosts file or Webseal that routed the request, as long as it can detect in the header (which it should be able to)

     

  • Hardy Wang 91 posts 112 karma points
    Mar 05, 2012 @ 15:46
    Hardy Wang
    0

    I used Request.ServerVariables to test the page behind WebSEAL, I got following key items

     

    SERVER_NAME123.123.123.123 {this is IP of my web server, if there is no WebSEAL I should get something like www.my-site.com}
    SERVER_PORT52443 (this is port of web site running in IIS)
    HTTP_HOST234.234.234.234:5678 {this is our WebSEAL's IP address, if there is no WebSEAL I should get something like www.my-site.com}

    Part of the request header sent from browser is

    Host:www.my-site.com:5678
    Referer:https://www.my-site.com:5678/

    So you can see web server in IIS is not able to capture exactly what is sent from browser.

    I would like to confirm in this scenario the Courier is still going to work or not.

    Thanks

     

Please Sign in or register to post replies

Write your reply to:

Draft