Re: Disable PHP ??? (was : Flash 11.x Plug-In Full Screen, crashing in FF, SM)

[Robert Kaiser]

Joe Rotello schrieb:

We have seen this "disable of one, some or all" of the mentioned
standards, Flash, PHP, JavaScript, even Java, happen, was the point, but
I have no wish or predilection for such to be done, as "web havoc" with
a side-order of "user fearanoia" always ensues.


Flash, PHP and Java are not standards. And even JavaScript isn't under 
that name, as the standard is called ECMAScript.


Still, you already handled PHP in there, it's server-side and not 
anything the client/browser needs to or even can care about. There's 
cases of server-side Java, for which the same applies. There's also 
websites running with Python (django, etc.), perl, node.js or any other 
number of technologies, which all are opaque to the user and nothing you 
ever need to care about unless you are operating web servers, and in 
this case you only need to worry about what you are operating there, not 
what others might run.


Flash and Java "applets" are browser plugins, essentially 
non-web-technology black boxes inside a web page, and in those black 
boxes there are binary third-party non-standard applications rendering 
some content that isn't accessible to the browser or web technologies.
This was a good idea for prototyping some functionality that earlier web 
browsers weren't able to do, but nowadays we (all browser vendors) are 
catching up fast with actual web technologies (HTML5 and friends) there, 
making the same kind of features better controllable for users (as 
browser functionality, prefs and add-ons like GreaseMonkey can access 
them) as well as easier to integrate in the experience of a website. We 
are at a point where those proprietary "black" boxes in websites like 
Flash and Java are increasingly unnecessary. Unfortunately, they're 
still around en masse, esp. in the case of Flash.


If you think you only need it rarely, or only on specific sites, it may 
be a good idea to try the experimental "click to play" feature that 
Firefox 14, SeaMonkey 2.11 and newer versions have integrated in a 
slightly hidden way (because it is experimental after all) - see the 
blog post of the developer when he first landed it for how to activate 
this feature: 
http://msujaws.wordpress.com/2012/04/11/opting-in-to-plugins-in-firefox/


Robert Kaiser
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Disable PHP ??? (was : Flash 11.x Plug-In Full Screen, crashing in FF, SM)

[WLS]

On 08/14/2012 08:14 AM, Joe Rotello wrote:
> On 8/14/2012 6:55 AM, support-seamonkey-requ...@lists.mozilla.org wrote:
> 
> Re: Disable PHP ??? (was : Flash 11.x Plug-In Full Screen
>   crashing    in FF, SM
> 
> 
> With all this discussion of stopping PHP from working, I scratch my head.
> 
> My main point was relating the Flash Plug-In crashing in many current FF
> and SM installations, and what was discussed with Adobe staffers
> regarding Flash 11.
> 
> We have seen this "disable of one, some or all" of the mentioned
> standards, Flash, PHP, JavaScript, even Java, happen, was the point, but
> I have no wish or predilection for such to be done, as "web havoc" with
> a side-order of "user fearanoia" always ensues.
> 
> My quite minor point was that ANY web standard...be it Flash, PHP,
> JavaScript, even Java, etc. can be disabled at one or more points,
> that's all, hence I mentioned it as a side-note to the Flash Plug-In
> crashing in many current FF and SM installations.
> 
> Joe

Sorry Joe, in a previous post you said PHP could be disabled in the
browser. I just wanted to know how you accomplished that, or how I
prevent the server from executing that PHP in the web page, when I
access it.

In other words, prove your point.

-- 
WaltS
Fedora 17 (64-bit)
GNOME 3.4.2
Thunderbird Beta
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Disable PHP ??? (was : Flash 11.x Plug-In Full Screen, crashing in FF, SM)

[Joe Rotello]

On 8/14/2012 6:55 AM, support-seamonkey-requ...@lists.mozilla.org wrote:

Re: Disable PHP ??? (was : Flash 11.x Plug-In Full Screen
  crashing  in FF, SM


With all this discussion of stopping PHP from working, I scratch my head.

My main point was relating the Flash Plug-In crashing in many current FF 
and SM installations, and what was discussed with Adobe staffers 
regarding Flash 11.


We have seen this "disable of one, some or all" of the mentioned 
standards, Flash, PHP, JavaScript, even Java, happen, was the point, but 
I have no wish or predilection for such to be done, as "web havoc" with 
a side-order of "user fearanoia" always ensues.


My quite minor point was that ANY web standard...be it Flash, PHP, 
JavaScript, even Java, etc. can be disabled at one or more points, 
that's all, hence I mentioned it as a side-note to the Flash Plug-In 
crashing in many current FF and SM installations.


Joe
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Disable PHP ??? (was : Flash 11.x Plug-In Full Screen crashing in FF, SM)

[David E. Ross]

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
.

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
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Disable PHP ??? (was : Flash 11.x Plug-In Full Screen crashing in FF, SM)

[Ray_Net]

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.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Disable PHP ??? (was : Flash 11.x Plug-In Full Screen crashing in FF, SM)

[David E. Ross]

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.

-- 

David E. Ross
.

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
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Disable PHP ??? (was : Flash 11.x Plug-In Full Screen crashing in FF, SM)

[Ed Mullen]

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


PHP runs on the server.  There is no way to disable it in a 
client/browser. When a browser asks for a PHP page the server assembles 
the page and sends it as Content-Type: text/html.  Open Live Http 
Headers and go to http://edmullen.net/index.php. Then view the source. 
See any php code in there?



--
Ed Mullen
http://edmullen.net/
What is a free gift? Aren't all gifts free?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Disable PHP ??? (was : Flash 11.x Plug-In Full Screen crashing in FF, SM)

[WLS]

On 08/13/2012 08: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

OK, I will bite.

Since PHP execution is done on the Server side (Apache, NGINX, etc.),
not the Client (Firefox, SeaMonkey, etc.). How does one go about
switching PHP execution off in the browser?

I already checked about:config in Firefox, and see no such preference.

-- 
WaltS
Fedora 17 (64-bit)
GNOME 3.4.2
Thunderbird Beta
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Disable PHP ??? (was : Flash 11.x Plug-In Full Screen crashing in FF, SM)

[Joe Rotello]

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
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Disable PHP ??? (was : Flash 11.x Plug-In Full Screen crashing in FF, SM)

[Philip TAYLOR]

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.

Philip Taylor

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey