----------------------------------------------------------- New Message on BDOTNET
----------------------------------------------------------- From: knswhiz Message 1 in Discussion Hi I am facing an issue with a certain architecture model for a requirement. I would greatly appreciate some quick help. We have a particular web based tool (OLAP tool hosted on IIS which talks to a SQL server database) hosted on a isolated environment (cannot accept Internet requests), isolated for many reasons. Now we need a cost effective way of letting Internet requests communicate with this web tool without compromising on the isolation of the box. The kind of approach we are presently doing is using another web application (intermediate) hosted on a different web server in the same network as the isolated box to talk to this web OLAP tool on the box. But this web server is open to Internet requests. The requests hitting the Intermediate web server should be processed and this server should send this processed request to the web tool in the isolated web server. Then the intermediate web server should get the response and then process the response and send it back to the client. Now, we have an issue regarding communicating server side events that the client browser might invoke, for instance, hitting on a button which might have some server side code behind for that aspx page. In fact, the issue lies in processing the request by the intermediate server. We use Context.Request to see the incoming request and HttpWebRequest as a new request object (giving the mapped URL as a parameter) which will serve as a outgoing request from intermediate server to the isolated server. We are unable to copy the contents of the incoming request object into this new request object. I would greatly appreciate if anyone could shed some light on a) if the approach is feasible b) if you have encountered a similar situation earlier and the proposed solution c) if there is any other alternatives to this situation besides this approach Summary of the Approach: The approach what we are following can be seen in four stages: 1) Capture the request from the client browser. (This is done using HTTPModules) 2) Process the Request which entails procuring the request (Context.Request) from the context in a fashion that it can be sent to the destination website (Analyzer2005) This is normally done by an HttpWebRequest instance which should get the details of the request from the Context.Request. The details include all that the Request object would contain including the headers, viewstate, etcÂ… This HttpWebRequest contains the copied request which needs to be sent to the destination website. 3) Manually get a response from the destination website (Analyzer2005) by sending this new processed request. (This is achieved by starting with a simple HttpWebRequest.GetResponse) 4) Output this response to the client. (Using a Streamreader) The response is processed before sending it to the client. ----------------------------------------------------------- To stop getting this e-mail, or change how often it arrives, go to your E-mail Settings. http://groups.msn.com/bdotnet/_emailsettings.msnw Need help? If you've forgotten your password, please go to Passport Member Services. http://groups.msn.com/_passportredir.msnw?ppmprop=help For other questions or feedback, go to our Contact Us page. http://groups.msn.com/contact If you do not want to receive future e-mail from this MSN group, or if you received this message by mistake, please click the "Remove" link below. On the pre-addressed e-mail message that opens, simply click "Send". Your e-mail address will be deleted from this group's mailing list. mailto:[EMAIL PROTECTED]
