PHP files without extension

[Berislav Lopac]

I know how to set Apache to send files with any extension to PHP before
sending a response. Is there a way to do so for files with no extension
whatsoever? I don't want *all* files to be parsed by PHP, but only those
without extension (and, of course, with some selected extensions).

Berislav

--
If the Internet is a Marx Brothers movie, and Web, e-mail, and IRC are
Groucho, Chico, and Harpo, then Usenet is Zeppo.

[Daniel Tryba]

Berislav Lopac <be************@dimedia.hr> wrote:

I know how to set Apache to send files with any extension to PHP before
sending a response. Is there a way to do so for files with no extension
whatsoever? I don't want *all* files to be parsed by PHP, but only those
without extension (and, of course, with some selected extensions).

Maybe you should take a look at MultiViews. This lets you write URLs
without extension and let Apache guess what file actually should be
used. http://example.com/foo will for example be evaluated to
http://example.com/foo.php if it exists or http://example.com/foo.html
instead...

--

Daniel Tryba

[Ian.H]

On Tue, 31 Aug 2004 12:03:12 +0200, "Berislav Lopac"
<be************@dimedia.hr> wrote:

I know how to set Apache to send files with any extension to PHP before
sending a response. Is there a way to do so for files with no extension
whatsoever? I don't want *all* files to be parsed by PHP, but only those
without extension (and, of course, with some selected extensions).

Berislav

If this is on a Unix box, just dropping the extension and providing you
have '<?php' at the top, the files should be parsed as PHP files.

Unlike windoze, Unix doesn't stupidly rely on the file extension to tell
the OS what the file is.

The other way would be to use mod_rewrite in Apache:
RewriteRule /^(files|you|wish|to|parse|as|php)$ /$1.php [L]
You'd save the files as foo.php etc, but access to '/foo' would then
read the 'foo.php' file without requiring the .php extension.
HTH =)

Regards,

Ian

--
Ian.H
digiServ Network
London, UK
http://digiserv.net/

[Berislav Lopac]

Ian.H wrote:

If this is on a Unix box, just dropping the extension and providing
you have '<?php' at the top, the files should be parsed as PHP files.
It doesn't work -- as I expected, it displays the PHP code. This is on a
Fedora box with Apache 1.3.29 -- perhaps this works in Apache 2?
The other way would be to use mod_rewrite in Apache:
RewriteRule /^(files|you|wish|to|parse|as|php)$ /$1.php [L]
You'd save the files as foo.php etc, but access to '/foo' would then
read the 'foo.php' file without requiring the .php extension.
HTH =)

It does help, but is there a way to do it via an AddType statement in the
httpd.conf, which AFAIK itself uses mod_rewrite?

Berislav

--
If the Internet is a Marx Brothers movie, and Web, e-mail, and IRC are
Groucho, Chico, and Harpo, then Usenet is Zeppo.

[Berislav Lopac]

Berislav Lopac wrote:

the httpd.conf, which AFAIK itself uses mod_rewrite?

Ooops, it turns out I don't know. It uses mod_mime, not mod_rewrite.

Berislav

--
If the Internet is a Marx Brothers movie, and Web, e-mail, and IRC are
Groucho, Chico, and Harpo, then Usenet is Zeppo.

[Ian.H]

On Tue, 31 Aug 2004 13:23:52 +0200, "Berislav Lopac"
<be************@dimedia.hr> wrote:

Ian.H wrote:

If this is on a Unix box, just dropping the extension and providing
you have '<?php' at the top, the files should be parsed as PHP files.

It doesn't work -- as I expected, it displays the PHP code. This is on a
Fedora box with Apache 1.3.29 -- perhaps this works in Apache 2?

Never used Apache2.. but you're right, it doesn't work for me either. I
must have confused that with something else a long time ago. Apologies
=)

The other way would be to use mod_rewrite in Apache:
RewriteRule /^(files|you|wish|to|parse|as|php)$ /$1.php [L]
You'd save the files as foo.php etc, but access to '/foo' would then
read the 'foo.php' file without requiring the .php extension.
HTH =)

It does help, but is there a way to do it via an AddType statement in the
httpd.conf, which AFAIK itself uses mod_rewrite?

Berislav

You could use AddType statements in vhost sections in httpd.conf or
within .htaccess files per-dir if preferred:
<Files foo>
ForceType application/x-httpd-php
</Files>
etc etc.. the just save the file as 'foo' and all should be sweet =)

HTH more.

Regards,

Ian

--
Ian.H
digiServ Network
London, UK
http://digiserv.net/

[Berislav Lopac]

Ian.H wrote:

You could use AddType statements in vhost sections in httpd.conf or
within .htaccess files per-dir if preferred:
<Files foo>
ForceType application/x-httpd-php
</Files>
etc etc.. the just save the file as 'foo' and all should be sweet =)

HTH more.

Nope, sorry. It still just shows the code...

I'm playing with aliases a bit, but I would still like to have a generic
parse via PHP be applied to filenames without extensions, if possible.

Berislav

--
If the Internet is a Marx Brothers movie, and Web, e-mail, and IRC are
Groucho, Chico, and Harpo, then Usenet is Zeppo.

[Berislav Lopac]

Ian.H wrote:

If this is on a Unix box, just dropping the extension and providing
you have '<?php' at the top, the files should be parsed as PHP files.

I have just discovered the strangest thing: if there is a file named foo.php
on the server, just calling /foo works!

E.g. http://localhost/foo = http://localhost/foo.php

Confused, but happy,

Berislav

--
If the Internet is a Marx Brothers movie, and Web, e-mail, and IRC are
Groucho, Chico, and Harpo, then Usenet is Zeppo.

[Jeffrey Silverman]

On Tue, 31 Aug 2004 10:39:25 +0000, Ian.H wrote:

If this is on a Unix box, just dropping the extension and providing you
have '<?php' at the top, the files should be parsed as PHP files.

Unlike windoze, Unix doesn't stupidly rely on the file extension to tell
the OS what the file is.

While the second part is true, the first part is not -- quite. Since
Apache is doing the parsing and not your Unix box, you *do* have to tell
Apache how to parse the files if you want them to be seen by the PHP
engine.

So I think that, as far as web serving goes, a similarly configured Apache
server on *either* Unix or Windows will work the same way. Because the OS
is not doing the parsing -- Apache is.

Not sure how you can configure PHP parsing for files with no extension,
but I would wager it can be done.

--
Jeffrey D. Silverman | je**********@jhu.edu **
Website | http://www.newtnotes.com

(** Drop "pants" to reply by email)

[Andy Hassall]

On Tue, 31 Aug 2004 13:23:52 +0200, "Berislav Lopac"
<be************@dimedia.hr> wrote:

It does help, but is there a way to do it via an AddType statement in the
httpd.conf,

Untested, but how about something like

<FilesMatch '^[^.]+$'>
ForceType application/x-httpd-php
</FilesMatch>

--
Andy Hassall / <an**@andyh.co.uk> / <http://www.andyh.co.uk>
<http://www.andyhsoftware.co.uk/space> Space: disk usage analysis tool

[Varavva Yevgen aka xa4anypu]

"Berislav Lopac" <be************@dimedia.hr> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ
ÓÌÅÄÕÀÝÅÅ: news:ch**********@ls219.htnet.hr...

Ian.H wrote:

If this is on a Unix box, just dropping the extension and providing
you have '<?php' at the top, the files should be parsed as PHP files.
I have just discovered the strangest thing: if there is a file named

foo.php on the server, just calling /foo works!

E.g. http://localhost/foo = http://localhost/foo.php

Confused, but happy,

Berislav

--
If the Internet is a Marx Brothers movie, and Web, e-mail, and IRC are
Groucho, Chico, and Harpo, then Usenet is Zeppo.

I have <quote>The requested URL /test was not found on this server.</quote>
though there is test.php

[Michael Fesser]

.oO(Berislav Lopac)

I have just discovered the strangest thing: if there is a file named foo.php
on the server, just calling /foo works!

E.g. http://localhost/foo = http://localhost/foo.php

Confused, but happy,

Nothing strange, this is called MultiViews. See the Apache manual entry
on "Content negotiation" for details.

<http://httpd.apache.org/docs/content-negotiation.html>

Micha

[John Dunlop]

Varavva Yevgen aka xa4anypu wrote:

I have <quote>The requested URL /test was not found on this server.</quote>
though there is test.php

'Note that Options All does not set MultiViews; you have to
ask for it by name.'

http://httpd.apache.org/docs/content-negotiation.html

Since it seems Berislav doesn't want URI suffixes, and isn't
concerned about file extensions, I second Daniel's
suggestion of considering MultiViews.

--
Jock