What if the file exists, but it's kinda file to update database, like

// get request $_REQUEST
// execute sql statement to update database
// redirect to the other page, showing results?

in this case 404 approach does not mean to do correctly, so what else is
suggested?

2009/1/22 Per Jessen <p...@computer.org>

> Richard Heyes wrote:
>
> >> ...
> >
> > Really, for URLs that don't exist you should be showing a 404, This
> > way the user doesn't falsely believe that the URL is a valid one and
> > keep using it. By using the ErrorDocument directive like Per
> > suggested, you can customise it to be distinct helpful
>
> Apache also comes with a good example of how to cobble that with content
> negotiation to present error documents in the users preferred language.
>
>
> /Per Jessen, Zürich
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

Reply via email to