perl installn..

Seite 1 von 1 - Forum: Coding Stuff auf overclockers.at

URL: https://www.overclockers.at/coding-stuff/perl_installn_27910/page_1 - zur Vollversion wechseln!

i krieg active perl in verbindung mitn apache einfach net zum laufn


also gegeben:

apache: c:\wamp\apache
perl: c:\usr\bin
htdocs verz: d:\www

i möcht, dass i für jedes unterverzeichnis in d:\www a eigenes cgi-bin brauch..

was muss i beim apache einstelln??

perl hab i per .msi file installiert..


am idealsten wär, wenn ma wer a httpd.conf schickn könnt..

thx mfg ska

Vielleicht findest du die Antwort im Google? Sorry, der musste einfach sein ... du 7TageohneInternetMensch

jaja habs ma eh gedacht, dass des kommt


brauchs aber für schul.. und so wies im apache manual steht hauts net hin.. krieg errorcode 403..

hab a paar andere manuals a scho gfunden, aber des haut a alles net hin...

ska hat mich gebeten, dass zu posten:

Code:

ServerType standalone

ServerRoot "C:/wamp/Apache"

PidFile logs/httpd.pid

ScoreBoardFile logs/apache_runtime_status

Timeout 300

KeepAlive On

MaxKeepAliveRequests 100

KeepAliveTimeout 15
MaxRequestsPerChild 0

ThreadsPerChild 50

Port 80

ServerAdmin [email]ska@cfx.at[/email]

ServerName [url]www.skawars.net[/url]

DocumentRoot "d:/www"

<Directory />
    Options FollowSymLinks
    AllowOverride None
</Directory>

<Directory "d:/www">

    Options Indexes FollowSymLinks MultiViews

    AllowOverride None

    Order allow,deny
    Allow from all
</Directory>

<IfModule mod_userdir.c>
    UserDir "C:/wamp/Apache/users/"
</IfModule>

#
# Control access to UserDir directories.  The following is an example
# for a site where these directories are restricted to read-only.
#
#<Directory "C:/wamp/Apache/users">
#    AllowOverride FileInfo AuthConfig Limit
#    Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
#    <Limit GET POST OPTIONS PROPFIND>
#        Order allow,deny
#        Allow from all
#    </Limit>
#    <LimitExcept GET POST OPTIONS PROPFIND>
#        Order deny,allow
#        Deny from all
#    </LimitExcept>
#</Directory>

#
# DirectoryIndex: Name of the file or files to use as a pre-written HTML
# directory index.  Separate multiple entries with spaces.
#
<IfModule mod_dir.c>
    DirectoryIndex index.html index.htm index.php
</IfModule>

#
# AccessFileName: The name of the file to look for in each directory
# for access control information.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess files from being viewed by
# Web clients.  Since .htaccess files often contain authorization
# information, access is disallowed for security reasons.  Comment
# these lines out if you want Web visitors to see the contents of
# .htaccess files.  If you change the AccessFileName directive above,
# be sure to make the corresponding changes here.
#
# Also, folks tend to use names such as .htpasswd for password
# files, so this will protect those as well.
#
<Files ~ "^\.ht">
    Order allow,deny
    Deny from all
</Files>

#
# CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each
# document that was negotiated on the basis of content. This asks proxy
# servers not to cache the document. Uncommenting the following line disables
# this behavior, and proxies will be allowed to cache the documents.
#
#CacheNegotiatedDocs

#
# UseCanonicalName:  (new for 1.3)  With this setting turned on, whenever
# Apache needs to construct a self-referencing URL (a URL that refers back
# to the server the response is coming from) it will use ServerName and
# Port to form a "canonical" name.  With this setting off, Apache will
# use the hostname:port that the client supplied, when possible.  This
# also affects SERVER_NAME and SERVER_PORT in CGI scripts.
#
UseCanonicalName On

#
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
#
<IfModule mod_mime.c>
    TypesConfig conf/mime.types
</IfModule>

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
# mod_mime_magic is not part of the default server (you have to add
# it yourself with a LoadModule [see the DSO paragraph in the 'Global
# Environment' section], or recompile the server and include mod_mime_magic
# as part of the configuration), so it's enclosed in an <IfModule> container.
# This means that the MIMEMagicFile directive will only be processed if the
# module is part of the server.
#
<IfModule mod_mime_magic.c>
    MIMEMagicFile conf/magic
</IfModule>

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., [url]www.apache.org[/url] (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog logs/error.log

#
# LogLevel: Control the number of messages logged to the error.log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here.  Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
CustomLog logs/access.log common

#
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#
#CustomLog logs/referer.log referer
#CustomLog logs/agent.log agent

#
# If you prefer a single logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog logs/access.log combined

#
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (error documents, FTP directory listings,
# mod_status and mod_info output etc., but not CGI generated documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of:  On | Off | EMail
#
ServerSignature On

# 
# Apache parses all CGI scripts for the shebang line by default.
# This comment line, the first line of the script, consists of the symbols
# pound (#) and exclamation (!) followed by the path of the program that 
# can execute this specific script.  For a perl script, with perl.exe in
# the C:\Program Files\Perl directory, the shebang line should be:

#!c:/usr/bin/


# Note you _must_not_ indent the actual shebang line, and it must be the
# first line of the file.  Of course, CGI processing must be enabled by 
# the appropriate ScriptAlias or Options ExecCGI directives for the files 

hab vorhin net posten können...

hier die jetzige conf

funkt des eine test-script?

wenn ja, hat's was mit deinen eigenen scripts...


bzgl jedem Ordner eigenes cgi-bin:
des wirds net spieln afaik...
wozu auch??

Zitat von ][Murph][

funkt des eine test-script?

wenn ja, hat's was mit deinen eigenen scripts...


bzgl jedem Ordner eigenes cgi-bin:
des wirds net spieln afaik...
wozu auch??

Code:

#!/usr/bin
print "Content-type: text/html\r\n\r\n";
print "Hello, World."; 

gib mal als shebangline

#!usr/bin/perl

nur testweise...


nochmals bzgl ordnern:
Was bringen dir 5 versch. CGI Ordner wenn du jeden einzeln ansprechen musst?

pack doch einfach alle scripts in den normalen rein, oder g0t keine dateibenennung?

dann wirds auch noch a bissi einfacher mim sichern etc.....

hmm mit /perl hinten geht leider a net...


kommentiert da apache net alles aus, was nach einem # steht??

wg verzeichnissen nochmal: najo.. is im prinzip egal, hauptsach i krieg des überhaupt amal zum gehn....

bzgl apache: jein
bzgl Perl: nein

es wird zwar nicht mitkompiliert,
aber du kannst so auch ein paar gewiefte coder verwirren:

man kann auch auskommentierte Lines bearbeiten,
zB mit einer regex
mit der regex nimmst dann das # raus, und siehe da, die line wird verarbeitet

nochmal bzgl server:
probier's mal mit indigoperl, oder zumindest schau da die config an.
das is ein fix fertiger apache mit perl 5.6.0 drauf, was für die meisten zwecke reichen sollte.

thx..


aber hat kaner an wamp mit perl laufn, der ma die conf schickn könnt?! kann des in da schul nämlich net runterladn.. und zhaus sin router u netzwerk deaktiviert

oja, a freund von mir...

kann ich aber erst spät abends erreichen, und dann nur per icq...
das heißt bis morgen früh hast es sicher...

Zitat von ][Murph][

oja, a freund von mir...

kann ich aber erst spät abends erreichen, und dann nur per icq...
das heißt bis morgen früh hast es sicher...

overclockers.at v4.thecommunity
© all rights reserved by overclockers.at 2000-2025