F
Flip Rayner
Hi,
We are creating a URL mapper that translates from one URL (yucky - badly
formatted), to a nicely formatted URL. The mapper acts as a proxy type
website above the source website, processing all incoming requests (in
nice URL format) and working out the appropriate source URL to request the
content on.
We are using the HTTPHandler object to intercept all webrequests, and
perform sub requests to the old website to retrieve the data to display
under the nice URL. We are finding that the mapper website is failing
after about 30minutes to 1 hour. The website mapper appears after a period
of time to return completely blank pages. Recycling the app pool fixed the
problem, but only for another 30 - 60 minutes. The w3wp.exe does not
appear to be using undue CPU, nor does the memory usage seem high or
excessive.
Has anyone else had similar problems with the HTTPHandler object? Is there
a timeout in the httpHandler that we need to be aware of?
Thanks,
We are creating a URL mapper that translates from one URL (yucky - badly
formatted), to a nicely formatted URL. The mapper acts as a proxy type
website above the source website, processing all incoming requests (in
nice URL format) and working out the appropriate source URL to request the
content on.
We are using the HTTPHandler object to intercept all webrequests, and
perform sub requests to the old website to retrieve the data to display
under the nice URL. We are finding that the mapper website is failing
after about 30minutes to 1 hour. The website mapper appears after a period
of time to return completely blank pages. Recycling the app pool fixed the
problem, but only for another 30 - 60 minutes. The w3wp.exe does not
appear to be using undue CPU, nor does the memory usage seem high or
excessive.
Has anyone else had similar problems with the HTTPHandler object? Is there
a timeout in the httpHandler that we need to be aware of?
Thanks,