The book I am reading describes exactly what you are talking about --
compiling a script into bytecode (like java). I have heard it described
as experimental by some people though.
-Dan
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> less acceptable on more and more web-sites. Prudence
> generally dictates 755 where other members of your group
> and the rest of the world can read and execute.
It is possible to use .htaccess files, apache config directives, and
burying 777 directories in 700 directories to add to the securi
> many ways to solve the problem. Amongst the real issues that
> the person will ultimately need to work out is whether it is
> really SANE to be writing temp files to begin with I mean
Yes! That is the other thing. If you write a script that writes temp
files you should consider it LOCAL ON
> Check to make sure that the script does not have control-M's at the end of
> every line. That will prevent it from executing.
FWIW, Windows file formats end all lines with a new line and a control
M. What text editor did you use to edit your script? It is possible
that it is ending all lines
Using the package command breaks up things into different namespaces.
For instance you could:
package my_package;
# do something
#do somethingelse
Puts both #do something and #do something else in the my_package
namespace. On the other hand:
{
package my_package;
# do something
}
#do somethi
If I create a cookie with path '/' does that mean it will be available
for all web pages on my site, or will it instead be only available to
web pages in the / directory?
Thanks in advance,
Dan
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Wed, 2003-11-19 at 15:30, Wiggins d Anconia wrote:
> Incidentally in this case it is the former. The path is meant to be a
> restrictor, so you are restricting the cookie to everything in said
> path, and since everything is in '/' then, well there you have it...
What if I don't supply a path
What is the best way to test a script that is spitting out stuff to the
httpd log. lessing a huge log is a PITA, and deleting it doesn't give
me a new log like I'd like (plus potentially loses information I need).
Thanks in advance,
Dan
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additio
I am having problems. I want a cgi script to call a perl script I
wrote, which is in the /var/www/cgi-bin directory, which is SUID root --
i.e. runs as root.
So I chmod +s the script and ran it like:
`./the_script`; in perl. The strangest thing happened though. I can't
+SUID something for root
On Thu, 2004-01-15 at 09:48, zentara wrote:
> On Tue, 13 Jan 2004 22:38:18 -0500, [EMAIL PROTECTED] (Gerry
> Creighton) wrote:
>
> >Hi,
> >I have a situation where I want people to upload large files to my
> >server after filling out a form with several fields. I have an uploader
> >form that
On Tue, 2004-01-13 at 16:05, R. Bryant wrote:
> Hi List,
>
> Is it possible to use CGI.pm in conjunction with a templating system?
Whenever you send out anything from your CGI object you'll do something
like this, correct?
my $cgi = CGI->new;
print $cgi->header;
Well you're *printing* anything
On Wed, 2004-01-21 at 01:45, Andrew Gaffney wrote:
> Dan Anderson wrote:
> > On Tue, 2004-01-13 at 16:05, R. Bryant wrote:
> >
> >>Hi List,
> >>
> >>Is it possible to use CGI.pm in conjunction with a templating system?
> >
> >
> > W
I want to create a HTML document that i can output the results of, and
also provide the file in XML format (i.e. not pretty printed in XML,
just data). Ideally I want the web page to display and then the user to
get a ("download product") dialog box to save the XML file.
I'm pretty sure that's po
13 matches
Mail list logo
