I'm sorry if this is the wrong place for this post, I just don't know where
else to go.
I need some help figuring out how to use FCGI_STDIN with a running php
script.
I have written a server in c++, which for a while been running php through
it's plain old cgi interface. I have been using php fo
Sara Golemon wrote:
The PDM recommendation covering the removal of safe_mode included a note
on expanding the role of open_basedir. To that end, I'd like to propose
introducing a new ini option: open_basedir_for_include which would allow
using include/require(_once) on an expanded set of direc
Hi.
Current pgsql.c supports prepared statement, but pg_execute() will raise
E_WARNING if query plan is not prepared yet. This is annoying when
database connection is persistent under web environment.
I would like to do something like
if (!pg_execute($db, 'myquery', array()) {
pg_prepare($db,
Yasuo Ohgaki wrote:
> 3) add bool parameter to pg_execute()
>e.g. pg_execute(resource connection, string stmtname, array params, bool
> ignore_error)
how would you intent to implement this?
AFAIK there is currently no catalog to find out the prepared statements
in the current sessions (I hea
>
> Sara Golemon wrote:
> > The PDM recommendation covering the removal of safe_mode included a
> > note on expanding the role of open_basedir. To that end,
> I'd like to
> > propose introducing a new ini option:
> open_basedir_for_include which
> > would allow using include/require(_once)
Why not just add the dirs you intend to include from to open_basedir
directly? It does not prevent arbitrary files from being loaded anyway
from those dirs. A simple ob_start() include "file"; ob_get_clean() will
happily give you the data. And if you wanted to see the source code,
highlight_fil
But it does prevent writing to those dirs.
Ilia Alshanetsky wrote:
Why not just add the dirs you intend to include from to open_basedir
directly? It does not prevent arbitrary files from being loaded anyway
from those dirs. A simple ob_start() include "file"; ob_get_clean() will
happily give y
Rasmus Lerdorf wrote:
But it does prevent writing to those dirs.
That should be the job of file permissions, let's use PEAR directory as
an example. In normal circumstances only the root user can write to
those dirs and everyone else has read-only access, therefor write
permission would alre
Ilia Alshanetsky wrote:
Rasmus Lerdorf wrote:
But it does prevent writing to those dirs.
That should be the job of file permissions, let's use PEAR directory as
an example. In normal circumstances only the root user can write to
those dirs and everyone else has read-only access, therefor wri
Rasmus Lerdorf wrote:
Yes, and in normal circumstances you wouldn't accidentally write to
places you aren't supposed to, just like in normal circumstances you
will have all your file permissions set correctly. And in normal
circumstances you would never have bugs in your code.
Attempts to mo
The PDM recommendation covering the removal of safe_mode included a note
on expanding the role of open_basedir. To that end, I'd like to propose
introducing a new ini option: open_basedir_for_include which would allow
using include/require(_once) on an expanded set of directories than what
ope
11 matches
Mail list logo
