Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You need to first evaluate whether it make sense to have image server under different domain. If its all about sharing the same code among multiple sites then you will be better off by putting you handler under site and sharing the relevant code via class library.</p> <p>There can be legitimate reasons for having handler on different domain. For example, it might need different level of scaling, it might be resource-hungry and you want to isolate it to different machine (isolating to different app-pool is possible under same domain) or because of some licensing issue (you want to save processor based license cost of some library used by handler).</p> <p>If there are going to be different domain then you can have them as sub-domains. For example - a.xyz.com and b.xyz.com. In such case, same authentication ticket (issued at parent domain i.e. xyz.com) will suffice for both. See <a href="http://msdn.microsoft.com/en-us/library/system.web.security.formsauthentication.cookiedomain.aspx" rel="nofollow">domain property for Forms Authentication Cookie</a> to control this.</p> <p>You also need to ask if authentication make sense for your image handler. Do you want it to be open or restricted to certain users? If you want only authenticated users and you want to support multiple applications then you are looking at supporting user sets of multiple applications. If it's the same user set (e.g. active directory) then your job will be simpler - have a single authentication provider whose ticket will be trusted by your site and all other applications [Windows Authentication works on similar basis]. </p> <p>If its diverse set of users then it essentially means that for image server, you have multiple authentication providers that you need to trusted. You probably need to look at some <a href="http://en.wikipedia.org/wiki/Federated_identity" rel="nofollow">Federated Identity</a> system - see one such .NET based implementation discussed here: <a href="http://msdn.microsoft.com/en-us/magazine/ff872350.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/magazine/ff872350.aspx</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. COIn the question i told about a.com in future i am going to have many application like c.com etc accessing the same image server. I also wanted to restrict b.com images from direct access. Can I check the request object to check from where the request is coming if it is from my web application a.com then it should serve the request if not then it should not serve the request.
      singulars
    2. CO@krshekhar, I am assuming that you talking about referrer field from request! Relying on such field can be problematic as it is easy for anyone to create counterfeit requests. Further, I am not certain from where call to b.com is going to originate from. So far I was assuming it to be from browser, but if b.com is directly accessed via a.com server code (as opposed to browser) then you really don't have much authentication issue - all you need to ensure is that call to b.com is made with correct user credentials.
      singulars
    3. COearlier I have created http handler on b.com now I want to move the handler on a.com (for authentication check). But for writing text on image I need the absolute path of the image("C:/Images/...") which can be get only on b.com (as I think). So do I need handlers at both the application. One for writing text (on b.com) and another for authentication user (on a.com). also I wanted to know how can I cast the http request to image on a.com. An how much performance will be affected by doing this.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload