There is a SharePoint farm with aroubd 5 web applications. Each web application has many site collections, and each site collection has many sites.
Some of the sites in each site collection will be used longer and when any request arrives in the site collection, it must be redirected to a new SharePoint URL in a different farm.
I am trying to implement an http handler or http module to catch requests that need to be redirected and redirected to a new URL.
However, I need to know:
Is using the Http handler or the Http module the best? The client cannot afford to have some custom web pages on the home pages of each site collection for redirection. Therefore, the request must be redirected before it reaches the page. Therefore, I assume that an Http handler or module is the best way.
What to choose between the Http handler and the Http module. I noticed that
a> If I go with the Http module, it is executed on each request to the web application. For example, if I just type the URL of a site collection in a browser, the Http module runs about 10 times. Could this be a performance issue?
b > Http- ( *.aspx), , , , Url , html . , , Http- (html), , , html , .
, .
,