By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,963 Members | 2,122 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,963 IT Pros & Developers. It's quick & easy.

Open-save .php file error instead of execute?

P: n/a
On one site I'm working on I occasionally get an error where instead
of executing the PHP file as per normal, the browser sees the page as
a file (therefore opens up a execute/save pop-up).

All these pages work fine locally on my Apache/WinXP but produces
these errors on the remote server (Linux/on Apache/1.3.34).

Where do I start looking?

I suspect there's some malformed headers being produced/sent as some
of the scripts use re-direction.

Or is it some basic Apache misconfiguration (it's on a remote hosted
server)?

Adam.
Jun 30 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Rik
Adam wrote:
On one site I'm working on I occasionally get an error where instead
of executing the PHP file as per normal, the browser sees the page as
a file (therefore opens up a execute/save pop-up).

All these pages work fine locally on my Apache/WinXP but produces
these errors on the remote server (Linux/on Apache/1.3.34).

Where do I start looking?

I suspect there's some malformed headers being produced/sent as some
of the scripts use re-direction.

Or is it some basic Apache misconfiguration (it's on a remote hosted
server)?


1. Check wether all your files end on .php after redirection (you could have
altered that locally, but that's not standard.
2. Try reading the error log of the server, and check what is's doing when
it serves the php as a normal file.

Grtz,
--
Rik Wasmus
Jun 30 '06 #2

P: n/a
On Fri, 30 Jun 2006 13:25:21 +0200, Rik wrote:
Adam wrote:
On one site I'm working on I occasionally get an error where instead
of executing the PHP file as per normal, the browser sees the page as
a file (therefore opens up a execute/save pop-up).

All these pages work fine locally on my Apache/WinXP but produces
these errors on the remote server (Linux/on Apache/1.3.34).

Where do I start looking?

I suspect there's some malformed headers being produced/sent as some
of the scripts use re-direction.

Or is it some basic Apache misconfiguration (it's on a remote hosted
server)?
1. Check wether all your files end on .php after redirection (you could have
altered that locally, but that's not standard.
2. Try reading the error log of the server, and check what is's doing when
it serves the php as a normal file.


Nothing there but .php files - I'm pretty strict on using all lower
case as well - as I'm developing on a WinXP system invariably for
Linux remote servers.

I'll try grabbing an error log - see if it gives me any clues.

Adam.
Jun 30 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.