Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Any disadvantage to using .php on a non-php page 1
- Thread starter CliveC
- Start date
![[cannon]](/data/assets/smilies/cannon.gif "[cannon] [cannon]")
gerrygerry
Technical User
Just a negligable processing time. -gerrygerry
Go To
Go To
ZollerWagner
Technical User
Would using a .php extension have any advantages? I'm all ears....
well if u dont have any php code i dont see any "advantage"
for giving the extension .php unless u suspect that the page will going to be dynamic in near future.
spookie --------------------------------------------------------------------------
I never set a goal because u never know whats going to happen tommorow.
for giving the extension .php unless u suspect that the page will going to be dynamic in near future.
spookie --------------------------------------------------------------------------
I never set a goal because u never know whats going to happen tommorow.
-
1
- #6
there is a slight disadvantage as gerrygerry mentionned but there might be a few more than we may think depending (I do say depending) on the way pages are processed on the server.
Gzip is a common zip program used by many apache servers. It zips the file to make it smaller when sent via the web. Browsers since version 3.0 can understand a zipped stream. If the extension is .htm .html .xhtml most apache servers are set up to automatically zip the file.
Here is how it happens.
Browser at IP 129.129.129.129 asks for >
server receives the request
>
zips the file for faster transfer (takes little time but packs files between 40%-95%)
>
sends it to 129.129.129.129
If the page is quite large it can save quite a considerable amount of time.
Now lots of servers out there are not set up to handle gzip with php. This means that when you process a page with php it might not be gzipped.
So your process would look like this :
Browser at IP 129.129.129.129 asks for >
server receives the request
>
sends the php file for processing (negligably fast process)
>
sends it to 129.129.129.129
I did a test for a file. It's size went from 3,576 to 1,424 bytes. This means a 2.5 times faster download!
If your server is not set up to gzip php files then it might not be that negligeable after all. You might want to check!
Gary Haran
Gzip is a common zip program used by many apache servers. It zips the file to make it smaller when sent via the web. Browsers since version 3.0 can understand a zipped stream. If the extension is .htm .html .xhtml most apache servers are set up to automatically zip the file.
Here is how it happens.
Browser at IP 129.129.129.129 asks for >
server receives the request
>
zips the file for faster transfer (takes little time but packs files between 40%-95%)
>
sends it to 129.129.129.129
If the page is quite large it can save quite a considerable amount of time.
Now lots of servers out there are not set up to handle gzip with php. This means that when you process a page with php it might not be gzipped.
So your process would look like this :
Browser at IP 129.129.129.129 asks for >
server receives the request
>
sends the php file for processing (negligably fast process)
>
sends it to 129.129.129.129
I did a test for a file. It's size went from 3,576 to 1,424 bytes. This means a 2.5 times faster download!
If your server is not set up to gzip php files then it might not be that negligeable after all. You might want to check!
Gary Haran- Thread starter
- #7
Thanks for a very well thought out and researched response Gary. Clive
- Status
