You could defined a different port in your tags. Then you can start
thttpd to bind to that port. You shouldn't have a problem binding to ports
higher that 1024(?) I think. Unless they have done something to prevent
this which is doubtful.
Example:
http://www.foo.com:/test/test.gif">
Unfo
> I have a high traffic website (looks like 200 GB output per month,
> something around 10-20 hits per day) hosted on a commercial
> service. The service does not limit my bandwidth usage, but they limit the
> number of concurrent Apache process that I can have to 41. This causes the
> ser
# Doesn't work. Children still get tied up serving requests.
#ProxyPass / http://www.animewallpapers.com:8080/
#ProxyPassReverse / http://www.animewallpapers.com:8080/
That doesn't get me around the limit of 41 Apache processes...
-Philip Mak ([EMAIL PROTECTED])
On Thu, 22 Feb 2001, Stathy Toul
Why don't you setup apache to do proxying?
> I have a high traffic website (looks like 200 GB output per month,
> something around 10-20 hits per day) hosted on a commercial
> service. The service does not limit my bandwidth usage, but they limit the
> number of concurrent Apache process
Hello,
I have a high traffic website (looks like 200 GB output per month,
something around 10-20 hits per day) hosted on a commercial
service. The service does not limit my bandwidth usage, but they limit the
number of concurrent Apache process that I can have to 41. This causes the
serve