sexy_guy

Well-Known Member
Mar 19, 2003
847
0
166
I have looked everywhere on the net for bwprotect_module and cannot find information on it anywhere.

My understanding of bwprotect is that when it is compiled in that it protect leechers and people from linking to your site to steal your bandwidth. That i understand, what i dont understand is why its installed on my servers and it doesnt work.

I have this;

Server Version: Apache/1.3.27 (Unix) mod_bwprotect/0.2 mod_log_bytes/1.2 mod_bwlimited/1.0 PHP/4.2.3 FrontPage/5.0.2.2510 mod_ssl/2.8.12 OpenSSL/0.9.6b
Server Built: Mar 8 2003 23:45:08

Which means its installed correct?

Ok so if our users go to;

http://123.45.67.890/~username/ they can load their sites

and if they go here

http://myhostname/~username/ they can also load their sites

Which is not right. Users should only be able to load their sites from

http://123.45.67.890/~username/ but as it stands right now they can load it from both URL's

User should only be able to preview their site from http://123.45.67.890/~username/ is that correct?

So the question is why? In order for bwprotect to work properly it has to be compiled in the the proper httpd.conf entries need to be in place and those are the follow

LoadModule bwprotect_module libexec/mod_bwprotect.so

&
AddModule mod_bwprotect.c

Let see what else, you also need;

ServerName myhostname.com

and you also need;

NameVirtualHost 123.45.67.890:80
Alias /bandwidth/ /usr/local/bandmin/htdocs/

<VirtualHost 123.45.67.890>
BytesLog domlogs/myhostname.com-bytes_log
ServerName myhostname.com
DocumentRoot /usr/local/apache/htdocs
</VirtualHost>

That should be about it.

Anyone who has this working, can you verify that this is correct?
 
Last edited:

Website Rob

Well-Known Member
Mar 23, 2002
1,501
1
318
Alberta, Canada
cPanel Access Level
Root Administrator
There had been some posts before DO switched to this bulletin board. Search for "UserDir public_html" and you should find them.

Basically, whether one is using 'mod_bwprotect' or not, this is the edit to make in the httpd.conf file:

<IfModule mod_userdir.c>
UserDir public_html
</IfModule>

And replace with:

UserDir disabled


Disabling UserDir has two disadvantages:

1) Use ~username with anything and it will not work.

2) Shared SSL could not be offered as https://secureserver.com/~username/


I have been using the above, without having 'mod_bwprotect' installed, and it works just fine -- Server-wide.
 

sexy_guy

Well-Known Member
Mar 19, 2003
847
0
166
Originally posted by Website Rob
There had been some posts before DO switched to this bulletin board. Search for "UserDir public_html" and you should find them.

Basically, whether one is using 'mod_bwprotect' or not, this is the edit to make in the httpd.conf file:

<IfModule mod_userdir.c>
UserDir public_html
</IfModule>

And replace with:

UserDir disabled


Disabling UserDir has two disadvantages:

1) Use ~username with anything and it will not work.

2) Shared SSL could not be offered as https://secureserver.com/~username/


I have been using the above, without having 'mod_bwprotect' installed, and it works just fine -- Server-wide.
That defeats the pupose of why its installed. We certainly need our users to share ssl and we need them to be able to use http://ip/~username to preview but not http://hostname/~username

:confused: