You could defined a different port in your <img> 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:
<img src="http://www.foo.com:6666/test/test.gif">
Unfortunately it could mean changing lots of code on your site. Of course,
you could use something like Apache::filter to alter your image tags on the
way out. I don't think this would be a difficult issue though. The main
thing is if you can bind to ports over 1024.
> > I have a high traffic website (looks like 200 GB output per month,
> > something around 100000-200000 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
> > server to delay accepting new connections during peak times.
> > My account is a "virtual server"; what this means is that I
> have access to
> > the Apache httpd.conf files and can restart the Apache daemon,
> but do not
> > have the priviledge to bind a program to port 80 (so I can't
> put thttpd on
> > port 80).
Stathy Touloumis
Coder
if ( eval{ $you => require Perl } ) { $you = '?3r1 H@c|<3r' }
Edventions
8800 Bronx Ave
Skokie, IL 60077
www.edventions.com
[EMAIL PROTECTED]
