Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
please don't use words like urgent. it's not urgent for us...
either way. just use a urlpath_regex acl to match the end of the file type IS you wish to block by a crude method like you are asking abou. better to block by mime type really i'd think.
but when i access ajhits.com or others mp3 downloading site, i can download mp3s
but i want to block downloading this files
thanks
if it's having no effect either you've not restarted squid or the entries are in the wrong place. you need to appreciate that with acl's in squid it will start at the top one and work down until a definite answer is received. you need to insert the http_access entry relative to your existing ones, probably fairly near the top of them. just make sure there are no rules above it to make it obselete, and it is not so high as to impact other rules below it. for example there is a default rule to allow the local machine to download anything. this is normally a very good thing. if this rule moves above it, that specific rule to permit 127.0.0.1 to do anything at all will no longer function.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.