PHTML

[Derek Broughton]

Markus Schönhaber wrote:

> Derek Broughton:
> 
>> Markus Schönhaber wrote:
> 
>>> Nothing you do on your local machine will change the behaviour of the
>>> > server for www.xplanner.org.
>> 
>> Nothing?  I find that really hard to believe, though I admit I'm having
>> some trouble myself...
> 
> I'm talking about the server's behaviour itself, not about circumventing
> the effects this behaviour (like using a proxy that changes the
> Content-Type header or whatever).
> If you can come up with a generally applicable way how I, just by
> fiddling around with my local machine, can manipulate other people's
> servers, please tell me. I'd be very interested.

But you shouldn't need to manipulate anybody else's server - your browser
should be capable of taking an "application/x-httpd-php" content type
(or "useless/garbage") and handling it the same way it handles "text/html".
 
>> I went through this with somebody else a while back, and he insisted his
>> custom type was correct - and hard to argue with him when IE was handling
>> it out of the box.
> 
> I have seen this more than once too. Nevertheless it's irrelevant in
> this case, since there's no "file extension" in http://www.xplanner.org/
> which Internet Exploder could use for it's "we don't care for standards
> - it's the extension which tells what type a file has in Windows and

Even IE handles the content type header.  It just happily handles pages
without a content type by mapping the file extension - so does konqueror. 
The thing that makes no sense to me is that 
  kfmclient openURL http://www.xplanner.org/ text/html
still doesn't work, though:
  wget http://www.xplanner.org/
  kfmclient openURL file:///`pwd`/index.html text/html
does. This proves there's nothing strictly in the file content to prevent a
browser opening it, and that's just the command that konqueror would use to
open a regular html page.

> therefore the same must be true on the internet" way of content type
> "detection".
> 
>> I'd be really surprised if it doesn't work for him...
> 
> I'd be surprised if it did.

I would have been surprised because it's hard to imagine anybody set up a
website without being able to read even the front page.  

In fact, it looks like he probably broke his apache configuration when
upgrading PHP.
-- 
derek