This is clearly turning into a topic of debate and I've received a PM about this today from a member who I won't name as they should have picked up on this in my previous post and really deserve a public flogging
Originally Posted by annonymous
Hope you don't mind the pm. I decided to pm rather than post because I thought maybe you could investigate this and if it's workable you could post a solution and if it's not you might tell me why so I can dismiss it.
Apparantly .php extention can be changed to anything eg .html. asp etc
Quote from my book:
Just change the line in your httpd.conf file that reads
AddType application/x-httpd-php .php
to whatever extension you please, such as
AddType application/x-httpd- .asp
Of course, you'll need ot eb sure that this does not cause conflict with other installed server technologies.
First of all
I don't personally understand this as I have never tried to do it so I have no idea if this is practical in the 'real world'. Sounds too easy, must be a catch.
You have a good understanding of php and how things work, maybe you can say whether this is workable or not.
You are correct in that .htaccess will allow this (and I've used it many times myself) but the op has said:
Originally Posted by 553311
Would someone please be able to provide a solution which works both in web browsers and in IIS.
IIS is microsofts http server not the http server from the apache foundation found on linux systems. There is a misconception that .htaccess is used by all webservers due to some sort of standard. I'm afraid I have big news for you: It's not! The http protocol is the standard webservers work to but how they do it and store their own configurations is not part of it is down to the authors.
.htaccess files are apache configuration files and IIS doesn't natively support them (AFAIK).
You can get them to work using ISAPI_Rewrite (which comes directly from the IIS.net forums
but thats a paid addition to IIS not a native part of it. You'd also need the server admin to install it.
IIS uses it's own configuration files that are in XML format and to be frank, it's horrible to use / look at / try to understand. There may be a IIS config program out there on google that makes them easy to generate but I'm afraid I never looked for one as I came up with another workaround for my problem at the time (which was totally different to the ops problem).
Apache became popular as it was basically written by nerds for nerds and was a skeleton web server that could use many different custom modules (hence it was named Apache because it was "a patchy
web server". With the huge number of additional modules and advanced configurations it could support it was only natural that it would become the most popular when offered on the free linux OS.
IIS however is a commercial offering from Microsoft who charge for it (either up front or hidden in the OS cost). While commercial usually means lots of advanced features it doesn't mean it will work in an identical manner to the free alternatives or even have the same features.
You can run cron on linux but if you tried on windows you'd be very disappointed because it's windows task scheduler and that works differently but does the same thing in a different manner