On 8/13/12 12:40 PM, Ray_Net wrote: > David E. Ross wrote, On 13/08/2012 18:28: >> On 8/13/12 5:22 AM, Joe Rotello wrote: >>> On 8/13/2012 6:52 AM, Philip TAYLOR wrote: >>>> Joe Rotello wrote: >>>> >>>>> JR Personal Reflection Bottom line: End-users who fully and >>>>> intentionally disable the likes of Flash plug-in, PHP, Java and even >>>>> JavaScript browser operations are in reality doing more to "damage" >>>>> their browser operations and shut themselves out of a great many needful >>>>> and useful web-sites world-wide. Many users who do the above and walk >>>>> away from those options then wonder why a great many web-sites and pages >>>>> no longer work or display properly, then start suspecting the browser or >>>>> the OS, etc. >>>> Whilst I have a /certain/ (but by no means unequivocal) sympathy with >>>> your position, I am completely at a loss to know how a user might seek >>>> to "disable ... PHP". PHP is a server-side technology, just like >>>> ASP and ASP.NET; how can this possibly be disabled client-side ? >>>> >>>> I would also argue that the vast majority of those who "do the above >>>> and walk away from those options" do not "wonder why a great many >>>> web-sites and pages no longer work or display properly" -- they know >>>> why, and they are prepared to live with this in order to satisfy their >>>> own security concerns and/or paranoia. >>> Like it or not, in many modern browsers, esp. those allowing access to >>> "about all" the settings, one can disrupt PHP operations, essentially >>> switching PHP execution off. Can be done in FF, for example, have seen >>> it accomplished in the OS with Internet Explorer, etc. >>> >>> Thankfully, people do NOT usually do this, nor should they, yet it can >>> be terribly exciting to troubleshoot a bad web experience and find out >>> that this kind of PHP disabling has been done. >>> >>> Yes, indeed, I tend to agree that many of those who do the above know >>> full well, or believe they do, of what they are doing, so PHP failures >>> or web-disasters should not come as a surprise to them. >>> >>> Joe >>> >> With the AdBlock Plus extension, it might be possible to block some PHP >> sites with a filter containing *.php. However, many Web sites today >> omit the file extension on the URIs; in that case, the filter will not >> work. >> > How can you disable PHP sites with AdBlock Plus When you ask for > http://edmullen.net/index.php > AdBlock will stop you ? Or it will stop the previous php site to send > you pure html code ? > > Anyway i don't understant why we should kill php sites. PHP sites cannot > attack your computer. >
Oops! Apparently, AdBlock Plus will NOT block a URI the user explicitly requests. No, I don't understand either why PHP sites should be blocked. I was trying to answer the question "How do you do it?" Perhaps I should have instead said, "Don't bother trying it.", especially since my AdBlock Plus suggestion does not work. -- David E. Ross <http://www.rossde.com/>. Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
