J
Jeff Dege
We have an app that is written in C#/ASP.NET 2.0, and hosted on IIS.
Or rather, it's mostly written in ASP.NET, but parts of it are client-
side javascript, pulling data from an Apache webserver in an ajax-like
fashion.
There is no chance of converting the Apache pages to run on IIS, or the
IIS pages to run on Apache, so we're inherently stuck with cross-domain
XMLHttpRequest() calls.
To this point, we've been running both IIS and Apache on different ports
on the same servers, and have had no problem. But we are concerned that
we will begin to see browsers that will reject calls to different ports.
And beyond that, we'd really like to try hosting Apache on a separate
box, better tuned for the sort of load that's being put on it.
That means we need a Web Proxy. And one that will run on IIS, and that
we can build, and maintain, with our current tool set (ASP.NET).
Problem is I've not been able to find one. There are plenty of simple
web proxies out there for Apache, and written in PHP, or CGI. But I've
not found an example of a simple web proxy for IIS written in ASP.NET.
I know people have had to have done this. But I've not been able to find
anything on the web. Is there some simple solution I've missed?
--
The government consists of a gang of men exactly like you and me. They
have, taking one with another, no special talent for the business of
government; they have only a talent for getting and holding office. Their
principal device to that end is to search out groups who pant and pine
for something they can't get and to promise to give it to them. Nine times
out of ten that promise is worth nothing. The tenth time is made good by
looting A to satisfy B. In other words, government is a broker in pillage,
and every election is sort of an advance auction sale of stolen goods.
- H. L. Mencken
Or rather, it's mostly written in ASP.NET, but parts of it are client-
side javascript, pulling data from an Apache webserver in an ajax-like
fashion.
There is no chance of converting the Apache pages to run on IIS, or the
IIS pages to run on Apache, so we're inherently stuck with cross-domain
XMLHttpRequest() calls.
To this point, we've been running both IIS and Apache on different ports
on the same servers, and have had no problem. But we are concerned that
we will begin to see browsers that will reject calls to different ports.
And beyond that, we'd really like to try hosting Apache on a separate
box, better tuned for the sort of load that's being put on it.
That means we need a Web Proxy. And one that will run on IIS, and that
we can build, and maintain, with our current tool set (ASP.NET).
Problem is I've not been able to find one. There are plenty of simple
web proxies out there for Apache, and written in PHP, or CGI. But I've
not found an example of a simple web proxy for IIS written in ASP.NET.
I know people have had to have done this. But I've not been able to find
anything on the web. Is there some simple solution I've missed?
--
The government consists of a gang of men exactly like you and me. They
have, taking one with another, no special talent for the business of
government; they have only a talent for getting and holding office. Their
principal device to that end is to search out groups who pant and pine
for something they can't get and to promise to give it to them. Nine times
out of ten that promise is worth nothing. The tenth time is made good by
looting A to satisfy B. In other words, government is a broker in pillage,
and every election is sort of an advance auction sale of stolen goods.
- H. L. Mencken