Open-save .php file error instead of execute?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Adam

    Open-save .php file error instead of execute?

    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 misconfiguratio n (it's on a remote hosted
    server)?

    Adam.
  • Rik

    #2
    Re: Open-save .php file error instead of execute?

    Adam wrote:[color=blue]
    > 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 misconfiguratio n (it's on a remote hosted
    > server)?[/color]

    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


    Comment

    • Adam

      #3
      Re: Open-save .php file error instead of execute?

      On Fri, 30 Jun 2006 13:25:21 +0200, Rik wrote:
      [color=blue]
      >Adam wrote:[color=green]
      >> 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 misconfiguratio n (it's on a remote hosted
      >> server)?[/color][/color]
      [color=blue]
      >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.[/color]

      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.

      Comment

      Working...