|
|
|
|
||||||
| alt.apache.configuration Apache web server configuration issues. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
I've installed 2.2.4 on Windows XP.
I've done the normal sweep through the httpd.conf file to set the various bits and pieces - my IP addy, my DocumentRoot, etc. In particular, I've set up a cgi-bin directory in the root of my site and I've configured Apache for this. However, dear Lord, I've spent the last DAY trying to make this work and it doesn't. I've even tried 2.0.59 and it behaves in the same way. Now, details, details; 1. I *know* my CGI isn't being executed because I've set it to bomb when it runs ( { char *c = 0; c = 0; } ). 2. The server is returning HTTP 500 - internal error. 3. The error log records "premature end of headers" - which is true clearly true in a sense - there couldn't have BEEN any headers since the CGI wasn't executed - but isn't useful in ing me work out WHY the CGI isn't executed. 4. The CGI debug log records the incoming request from the browser, and it looks fine, but records no output from the binary (which makes sense). The relevant lines from my httpd.conf are; DocumentRoot "c:/data/html/summerblue.net" ScriptAlias /cgi-bin/ "c:/data/html/summerblue.net/cgi-bin/" <Directory "c:/data/html/summerblue.net/cgi-bin"> AllowOverride None Options None Order allow,deny Allow from all </Directory> So - anyone - PLEASE - I'm going crazy over this! |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
Toby Douglass wrote:
(snipped) > In particular, I've set up a cgi-bin directory in the root of my site > and I've configured Apache for this. > However, dear Lord, I've spent the last DAY trying to make this work and > it doesn't. I've even tried 2.0.59 and it behaves in the same way. > DocumentRoot "c:/data/html/summerblue.net" > ScriptAlias /cgi-bin/ "c:/data/html/summerblue.net/cgi-bin/" AddHandler cgi-script cgi > <Directory "c:/data/html/summerblue.net/cgi-bin"> > AllowOverride None > Options None Options +ExecCGI http://www.purlgurl.net/manual/howto/cgi.html Your cgi script must run correctly, must print a content type header such as plaintext or html, and have your script print a return. "Hello World" seems a favorite. Purl Gurl |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
purlgurl@purlgurl.net wrote:
> Toby Douglass wrote: > > DocumentRoot "c:/data/html/summerblue.net" > > ScriptAlias /cgi-bin/ "c:/data/html/summerblue.net/cgi-bin/" > > AddHandler cgi-script cgi I've tried that, although the exact line was; AddHandler cgi-script .exe The docs say ScriptAlias is enough though, in that anything in a ScriptAlias directory is executed as a CGI rather than supplied as a document; AddHandler is for use with ExecCGI. > > <Directory "c:/data/html/summerblue.net/cgi-bin"> > > AllowOverride None > > Options None > > Options +ExecCGI Tried that too, with and without AddHandler. (E.g. I tried the Directory/AddHandler/Options route, not just ScriptAlias. Still no go). > http://www.purlgurl.net/manual/howto/cgi.html I'll check this out and see what it says. > Your cgi script must run correctly, must print a content type > header such as plaintext or html, and have your script print > a return. "Hello World" seems a favorite. The CGI, prior to me rigging it to bomb so I could see if it was being called, returned "Content-type: text/html\n\n" and then a very simple HTML page. It ran fine from the command line when executed independently. |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
"Toby Douglass" <toby.douglass@youknowwhattodo.summerblue.net> schreef in
bericht news:MPG.20bdfa203887581f9896bc@news.cable.ntlworl d.com... >> Toby Douglass wrote: >> > DocumentRoot "c:/data/html/summerblue.net" >> > ScriptAlias /cgi-bin/ "c:/data/html/summerblue.net/cgi-bin/" >> AddHandler cgi-script cgi > > I've tried that, although the exact line was; > AddHandler cgi-script .exe > Looks like you want to execute a binary, rather than a script. A script normally has a reference to the interpreter in the first line, your executable does not. On linux I'ld try a empty script pointing to the executable as if this executable is the interpreter to run that script. On Windows try your luck with ScriptInterpreterSource Registry[-Strict] http://httpd.apache.org/docs/2.2/mod...erpretersource Note: Unless your program spits its complains to STDERR apache's error.log will not show a trace of its mailfunction. HansH |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
hansh@invalid.invalid wrote:
> "Toby Douglass" <toby.douglass@youknowwhattodo.summerblue.net> schreef in > > I've tried that, although the exact line was; > > AddHandler cgi-script .exe > Looks like you want to execute a binary, rather than a script. Yes. > A script normally has a reference to the interpreter in the first line, your > executable does not. Also yes. This means then that ScriptAlias is for true scripts only, not for "scripts" in the generic sense of things-you-can-execute? > On linux I'ld try a empty script pointing to the executable as if this > executable is the interpreter to run that script. > > On Windows try your luck with > ScriptInterpreterSource Registry[-Strict] > http://httpd.apache.org/docs/2.2/mod...erpretersource Well, what I'll do is stop trying to make ScriptAlias work. The impression I had from the docs was that ScriptAlias was the right way to configure for CGI. It appears to be so only for true scripts. For binaries, you presumably need ExecCGI and AddHandler...although I've tried them and they don't work either! but I'll try some more. > Note: Unless your program spits its complains to STDERR apache's error.log > will not show a trace of its mailfunction. Ah, ta. But I know the exe isn't executing, because it's rigged to bomb when it's called. |
|
|
|
#6 |
|
Messages: n/a
Hébergeur: |
"Toby Douglass" <toby.douglass@youknowwhattodo.summerblue.net> schreef in
bericht news:MPG.20be8e37d4e1d74e9896bd@news.cable.ntlworl d.com... > hansh@invalid.invalid wrote: >> "Toby Douglass" <toby.douglass@youknowwhattodo.summerblue.net> schreef in >> On Windows try your luck with >> ScriptInterpreterSource Registry[-Strict] >> http://httpd.apache.org/docs/2.2/mod...erpretersource > > Well, what I'll do is stop trying to make ScriptAlias work. The > impression I had from the docs was that ScriptAlias was the right way to > configure for CGI. It appears to be so only for true scripts. It should do for binaries too ... quite to my surprice... > For binaries, you presumably need ExecCGI and AddHandler... http://httpd.apache.org/docs/2.2/handler.html: the name given with this directive is a reference to a routine made available by one of the modules loaded by apache. IOW to use this method you have to convert your executable into an apache plug-in ... This paragraph might be of interest http://httpd.apache.org/docs/2.2/howto/cgi.html#writing > But I know the exe isn't executing, because it's rigged to bomb when > it's called. Your bomb wil only bang deep down below the surface ... Just create a program writing these 3 lines to standerd output: Content-type: text/plain Hello, TD -the second line is blank- and (re)start from there! HansH |
|
|
|
#7 |
|
Messages: n/a
Hébergeur: |
hansh@invalid.invalid wrote:
> "Toby Douglass" <toby.douglass@youknowwhattodo.summerblue.net> schreef: Okay, I've got CGI working now. This post is for Usenet archival purposes, for other people with the same problem. > > Well, what I'll do is stop trying to make ScriptAlias work. The > > impression I had from the docs was that ScriptAlias was the right way to > > configure for CGI. It appears to be so only for true scripts. > It should do for binaries too ... quite to my surprice... And indeed it does. > > But I know the exe isn't executing, because it's rigged to bomb when > > it's called. > Your bomb wil only bang deep down below the surface ... And indeed this is true, quite to my surprise! I thought that if a binary crashed, it crashed, and that was that - you'd get a dialog box of some sort from the OS. In fact, this is not so. Apache I suspect is suppressing the OS in this regard. So, as I said, it's working now. I'm not quite sure HOW, since I'm pretty certain the httpd.conf I have now is EXACTLY one I had earlier. My current httpd.conf is quoted below for anyone else with the same problem. Hans - thankyou for your time and ! # # This is the main Apache HTTP server configuration file. It contains the # configuration directives that give the server its instructions. # See <URL:http://httpd.apache.org/docs/2.2/> for detailed information. # In particular, see # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html> # for a discussion of each configuration directive. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with "/" (or "drive:/" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so "logs/foo.log" # with ServerRoot set to "C:/Program Files/Apache Software Foundation/Apache2.2" will be interpreted by the # server as "C:/Program Files/Apache Software Foundation/Apache2.2/logs/foo.log". # # NOTE: Where filenames are specified, you must use forward slashes # instead of backslashes (e.g., "c:/apache" instead of "c:\apache"). # If a drive letter is omitted, the drive on which Apache.exe is located # will be used by default. It is recommended that you always supply # an explicit drive letter in absolute paths, however, to avoid # confusion. # # ThreadsPerChild: constant number of worker threads in the server process # MaxRequestsPerChild: maximum number of requests a server process serves ThreadsPerChild 16 MaxRequestsPerChild 0 ServerRoot "C:/Program Files/Apache Software Foundation/Apache2.2" Listen localhost:80 # Dynamic Shared Object (DSO) Support # # To be able to use the functionality of a module which was built as a DSO you # have to place corresponding `LoadModule' lines at this location so the # directives contained in it are actually available _before_ they are used. # Statically compiled modules (those listed by `httpd -l') do not need # to be loaded here. # # Example: # LoadModule foo_module modules/mod_foo.so LoadModule actions_module modules/mod_actions.so LoadModule alias_module modules/mod_alias.so LoadModule asis_module modules/mod_asis.so LoadModule auth_basic_module modules/mod_auth_basic.so #LoadModule auth_digest_module modules/mod_auth_digest.so #LoadModule authn_anon_module modules/mod_authn_anon.so #LoadModule authn_dbm_module modules/mod_authn_dbm.so LoadModule authn_default_module modules/mod_authn_default.so LoadModule authn_file_module modules/mod_authn_file.so #LoadModule authz_dbm_module modules/mod_authz_dbm.so LoadModule authz_default_module modules/mod_authz_default.so LoadModule authz_groupfile_module modules/mod_authz_groupfile.so LoadModule authz_host_module modules/mod_authz_host.so LoadModule authz_user_module modules/mod_authz_user.so LoadModule autoindex_module modules/mod_autoindex.so #LoadModule cern_meta_module modules/mod_cern_meta.so LoadModule cgi_module modules/mod_cgi.so #LoadModule dav_module modules/mod_dav.so #LoadModule dav_fs_module modules/mod_dav_fs.so #LoadModule deflate_module modules/mod_deflate.so LoadModule dir_module modules/mod_dir.so LoadModule env_module modules/mod_env.so #LoadModule expires_module modules/mod_expires.so #LoadModule file_cache_module modules/mod_file_cache.so #LoadModule headers_module modules/mod_headers.so LoadModule imagemap_module modules/mod_imagemap.so LoadModule include_module modules/mod_include.so #LoadModule info_module modules/mod_info.so LoadModule isapi_module modules/mod_isapi.so LoadModule log_config_module modules/mod_log_config.so LoadModule mime_module modules/mod_mime.so #LoadModule mime_magic_module modules/mod_mime_magic.so #LoadModule proxy_module modules/mod_proxy.so #LoadModule proxy_ajp_module modules/mod_proxy_ajp.so #LoadModule proxy_balancer_module modules/mod_proxy_balancer.so #LoadModule proxy_connect_module modules/mod_proxy_connect.so #LoadModule proxy_http_module modules/mod_proxy_http.so #LoadModule proxy_ftp_module modules/mod_proxy_ftp.so LoadModule negotiation_module modules/mod_negotiation.so #LoadModule rewrite_module modules/mod_rewrite.so LoadModule setenvif_module modules/mod_setenvif.so #LoadModule speling_module modules/mod_speling.so #LoadModule status_module modules/mod_status.so #LoadModule unique_id_module modules/mod_unique_id.so LoadModule userdir_module modules/mod_userdir.so #LoadModule usertrack_module modules/mod_usertrack.so #LoadModule vhost_alias_module modules/mod_vhost_alias.so #LoadModule ssl_module modules/mod_ssl.so ServerAdmin a@b.com ServerName localhost:80 # # DocumentRoot: The directory out of which you will serve your # documents. By default, all requests are taken from this directory, but # symbolic links and aliases may be used to point to other locations. # DocumentRoot "c:/data/html/summerblue.net" # Each directory to which Apache has access can be configured with respect # to which services and features are allowed and/or disabled in that # directory (and its subdirectories). # # First, we configure the "default" to be a very restrictive set of # features. # <Directory /> Options FollowSymLinks AllowOverride None Order deny,allow Deny from all Satisfy all </Directory> # Note that from this point forward you must specifically allow # particular features to be enabled - so if something's not working as # you might expect, make sure that you have specifically enabled it # below. # # This should be changed to whatever you set DocumentRoot to. # <Directory "c:/data/html/summerblue.net"> # # Possible values for the Options directive are "None", "All", # or any combination of: # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews # # Note that "MultiViews" must be named *explicitly* --- "Options All" # doesn't give it to you. # # The Options directive is both complicated and important. Please see # http://httpd.apache.org/docs/2.2/mod/core.html#options # for more information. # Options Indexes FollowSymLinks # # AllowOverride controls what directives may be placed in .htaccess files. # It can be "All", "None", or any combination of the keywords: # Options FileInfo AuthConfig Limit # AllowOverride None Order allow,deny Allow from all </Directory> # # DirectoryIndex: sets the file that Apache will serve if a directory # is requested. # <IfModule dir_module> DirectoryIndex index.html </IfModule> # # The following lines prevent .htaccess and .htpasswd files from being # viewed by Web clients. # <FilesMatch "^\.ht"> Order allow,deny Deny from all </FilesMatch> # # 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 <IfModule log_config_module> # # 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 <IfModule logio_module> # You need to enable mod_logio.c to use %I and %O LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User- Agent}i\" %I %O" combinedio </IfModule> # # 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 prefer a logfile with access, agent, and referer information # (Combined Logfile Format) you can use the following directive. # #CustomLog logs/access.log combined </IfModule> <IfModule alias_module> ScriptAlias /cgi-bin/ "c:/data/html/summerblue.net/cgi-bin/" </IfModule> # # "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin" should be changed to whatever your ScriptAliased # CGI directory exists, if you have that configured. # <Directory "c:/data/html/summerblue.net/cgi-bin"> AllowOverride None Options None Order allow,deny Allow from all </Directory> # # 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:/program files/perl/perl # 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 # or directory in question. # # However, Apache on Windows allows either the Unix behavior above, or can # use the Registry to match files by extention. The command to execute # a file of this type is retrieved from the registry by the same method as # the Windows Explorer would use to handle double-clicking on a file. # These script actions can be configured from the Windows Explorer View menu, # 'Folder Options', and reviewing the 'File Types' tab. Clicking the Edit # button allows you to modify the Actions, of which Apache 1.3 attempts to # perform the 'Open' Action, and failing that it will try the shebang line. # This behavior is subject to change in Apache release 2.0. # # Each mechanism has it's own specific security weaknesses, from the means # to run a program you didn't intend the website owner to invoke, and the # best method is a matter of great debate. # # To enable the this Windows specific behavior (and therefore -disable- the # equivilant Unix behavior), uncomment the following directive: # #ScriptInterpreterSource registry # # The directive above can be placed in individual <Directory> blocks or the # .htaccess file, with either the 'registry' (Windows behavior) or 'script' # (Unix behavior) option, and will override this server default option. # # # DefaultType: 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 <IfModule mime_module> # # TypesConfig points to the file containing the list of mappings from # filename extension to MIME-type. # TypesConfig conf/mime.types # # AddType allows you to add to or override the MIME configuration # file specified in TypesConfig for specific file types. # #AddType application/x-gzip .tgz # # AddEncoding allows you to have certain browsers uncompress # information on the fly. Note: Not all browsers support this. # #AddEncoding x-compress .Z #AddEncoding x-gzip .gz .tgz # # If the AddEncoding directives above are commented-out, then you # probably should define those extensions to indicate media types: # AddType application/x-compress .Z AddType application/x-gzip .gz .tgz # # AddHandler allows you to map certain file extensions to "handlers": # actions unrelated to filetype. These can be either built into the server # or added with the Action directive (see below) # # To use CGI scripts outside of ScriptAliased directories: # (You will also need to add "ExecCGI" to the "Options" directive.) # #AddHandler cgi-script .cgi # For type maps (negotiated resources): #AddHandler type-map var # # Filters allow you to process content before it is sent to the client. # # To parse .shtml files for server-side includes (SSI): # (You will also need to add "Includes" to the "Options" directive.) # #AddType text/html .shtml #AddOutputFilter INCLUDES .shtml </IfModule> # # 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. # #MIMEMagicFile conf/magic # # Customizable error responses come in three flavors: # 1) plain text 2) local redirects 3) external redirects # # Some examples: #ErrorDocument 500 "The server made a boo boo." #ErrorDocument 404 /missing.html #ErrorDocument 404 "/cgi-bin/missing_handler.pl" #ErrorDocument 402 http://localhost/subscription_info.html # # # EnableMMAP and EnableSendfile: On systems that support it, # memory-mapping or the sendfile syscall is used to deliver # files. This usually improves server performance, but must # be turned off when serving from networked-mounted # filesystems or if support for these functions is otherwise # broken on your system. # #EnableMMAP off #EnableSendfile off # Supplemental configuration # # The configuration files in the conf/extra/ directory can be # included to add extra features or to modify the default configuration of # the server, or you may simply copy their contents here and change as # necessary. # Server-pool management (MPM specific) #Include conf/extra/httpd-mpm.conf # Multi-language error messages #Include conf/extra/httpd-multilang-errordoc.conf # Fancy directory listings #Include conf/extra/httpd-autoindex.conf # Language settings #Include conf/extra/httpd-languages.conf # User home directories #Include conf/extra/httpd-userdir.conf # Real-time info on requests and configuration #Include conf/extra/httpd-info.conf # Virtual hosts #Include conf/extra/httpd-vhosts.conf # Local access to the Apache HTTP Server Manual #Include conf/extra/httpd-manual.conf # Distributed authoring and versioning (WebDAV) #Include conf/extra/httpd-dav.conf # Various default settings #Include conf/extra/httpd-default.conf # Secure (SSL/TLS) connections #Include conf/extra/httpd-ssl.conf # # Note: The following must must be present to support # starting without SSL on platforms with no /dev/random equivalent # but a statically compiled-in mod_ssl. # <IfModule ssl_module> SSLRandomSeed startup builtin SSLRandomSeed connect builtin </IfModule> |
|
![]() |
| Outils de la discussion | |
|
|