PDA

View Full Version : Homeserver is acting up with php

Nblufire12
12-04-2008, 01:06 AM
hey guys

i am hosting my site, www.tindorafarms.com which is a proxy

however, just TODAY, i am getting this weird error, if you go there, its all in text and not the real site...whats going on?

Fou-Lu
12-04-2008, 01:09 AM

ptmuldoon
12-04-2008, 01:10 AM
Hard to say. Your running a home server. What software you using? Did you reboot the server? It looks like an issue with either your apache or php configuration.

Fou-Lu. The page is a mess. Here's the first 4 rows of the page:

'q', 'flags_var_name' => 'hl', 'get_form_name' => '____pgfa', 'basic_auth_var_name' => '____pbavn', 'max_file_size' => -1, 'allow_hotlinking' => 0, 'upon_hotlink' => 1, 'compress_output' => 0 ); $_flags = array ( 'include_form' => 1, 'remove_scripts' => 1, 'accept_cookies' => 1, 'show_images' => 1, 'show_referer' => 1, 'rotate13' => 0, 'base64_encode' => 1, 'strip_meta' => 1, 'strip_title' => 0, 'session_cookies' => 1 );$_frozen_flags = array ( 'include_form' => 0, 'remove_scripts' => 0, 'accept_cookies' => 0, 'show_images' => 0, 'show_referer' => 0, 'rotate13' => 0, 'base64_encode' => 0, 'strip_meta' => 0, 'strip_title' => 0, 'session_cookies' => 0 ); \$_labels = array ( 'include_form' => array('Include Form', 'Include mini URL-form on every page'), 'remove_scripts' => array('Remove Scripts', 'Remove client-side scripting (i.e JavaScript)'), 'accept_cookies' => array('Accept Cookies', 'Allow cookies to be stored'), 'show_images' => array('Show Images', 'Show images on browsed pages'),

oracleguy
12-04-2008, 01:16 AM
You need to provide more information, most notably which web server you are using and what you did to install php.

Fou-Lu
12-04-2008, 01:20 AM
Its hard to say if this is just a dumpout with a print_r on legit code, or it its malecious code thats being printed for debugging.
I'd replace the served source with you're original source and check you're access logs for more information.
If it just started up it and you made no changes, I'd be pretty leary. Of course, restart you're apache server first, if the same data is displayed, you need to edit you're files immediately to determine what the problem is.

Lol, thats funny. I didn't even notice it wasn't parsed :P

Nblufire12
12-04-2008, 01:56 AM
Sorry I cant believe i didnt put it in

I'm using Xampp

The Latest Version, It worked on a 1and1.com server, but not my home server...
watsup!?!?

Nblufire12
12-04-2008, 02:50 AM
I re-installed Xampp, but still didnt work, i have no clue what the problem is.

Fou-Lu
12-04-2008, 02:57 AM
Create a page for php info.

<?php

php_info();

?>

You'll know if its processing (it will list everything for PHP configurations). If it just shows php_info(), the page is not being parsed.
There are a few possible causes:
- PHP is not installed/enabled
- .php hasn't been set up to handle PHP requests. (assuming you're extension is .php)
- Check you're error logs. Apache on windows tends to choke if it can't find something. You can get to it from \\Apache\logs\error.log I belive it is, where \\Apache is wherever you're root apache install is. Navigate to you're AMPs and drill down for apache. I've never used any of the AMPs but I'd assume they would still keep everything separate. If XAMPP is a Linux technology, search for /etc/httpd/logs I believe it is.

Nblufire12
12-04-2008, 02:59 AM
kk try it out tindorafarms.com

crap i shulda thought of that lol

ur amazin!

php doesnt work!!! why?

Fou-Lu
12-04-2008, 03:00 AM
What is the file extension you're using?

And can you tell me if this is windows or linux, and where the apache (or even the xampp) is installed?

Nblufire12
12-04-2008, 03:01 AM
I am using php, index.php

this is windows

xampp is installed in

C:\Xampp

Fou-Lu
12-04-2008, 03:07 AM
From C:\XAmpp drill down looking for Apache\conf\httpd.conf
Open that file for editing.
You're looking for a couple of things (I'm not on a computer I can check this at, so you'll need to bare with me and maybe wait until I can get home or another member replied):
Load_module - There should be one loaded for phpX_module (where x is the version, pointed to an .so file)
AddType - There should be an entry for PHP. Looks like: AddType application/x-httpd-php .php

Anything with a # next to it (on the left at the start of the line) is a comment. So you'll want to ensure that these haven't been commented out.

If these look ok, check both you're Windows alert logger and the Apache logs. See if apache is dying when its trying to load the actual files.

Nblufire12
12-04-2008, 03:27 AM
Heres my httpd.conf

#
# 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:/xampp/apache" will be interpreted by the
# server as "C:/xampp/apache/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# 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.
#

# MaxRequestsPerChild: maximum number of requests a server process serves
MaxRequestsPerChild 0

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "C:/xampp/apache"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
Listen 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
#
# Example:
#

#<IfModule ssl_module>
#</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. admin@your-domain.com
#

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
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:/xampp/htdocs"

#
# 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 />
AllowOverride None
Order deny,allow
Deny from 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:/xampp/htdocs">
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
#
# 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
#

#
# 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 All

#
# Controls who can get stuff from this server.
#
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.php index.php4 index.php3 index.cgi index.pl index.html index.htm index.shtml index.phtml
</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,
#
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>
#
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar

#
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
#
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# the filesystem path.

#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
#
ScriptAlias /cgi-bin/ "C:/xampp/cgi-bin/"

</IfModule>

#
# "C:/xampp/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "C:/xampp/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.
#
#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#
#
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#

#
# 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.)
#

# For files that include their own HTTP headers:

# For server-parsed imagemap files:

# For type maps (negotiated resources):

#
# 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.)
#
</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://www.example.com/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
#
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.

# XAMPP specific settings
Include conf/extra/httpd-xampp.conf

# 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

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>

owt200x
12-04-2008, 03:32 AM
You could always uninstall XAmpp and install VertrigoServ instead, thats what i use to test php before publishing, but it is also usefull as a production server.

Fou-Lu
12-04-2008, 03:44 AM
Looks like PHP's not configured.
In you're dynamic shared objects (the LoadModule part), add this (with the corresponding PHP version you have in use):

X will correspond to you're PHP version, Y to you're apache version. If its new, it will be PHP5 and apache 2.

Then, find this:
<IfModule mime_module>

And (I usually stick it at the bottom, but it shouldn't really matter) add this:

Restart apache (or xampp) and try to access the php info page again.

If that doesn't work, check error logs (it may be a path or read problem on the dll for the php).

Post back you're results.

Nblufire12
12-04-2008, 12:43 PM
I did this but it still won't show my php info..should I post my httpd.conf

Fou-Lu
12-04-2008, 06:34 PM
Yep.
Did you check you're windows even log viewer as well as the apache logs to see if there is a problem loading the PHP module?

Nblufire12
12-04-2008, 06:41 PM
heres my httpd.conf

i am not home but i moved my site to tindorafarms.com hosted by *************** and it doesnt look like its working either..

#
# 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:/xampp/apache" will be interpreted by the
# server as "C:/xampp/apache/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# 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.
#

# MaxRequestsPerChild: maximum number of requests a server process serves
MaxRequestsPerChild 0

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "C:/xampp/apache"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
Listen 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
#
# Example:
#

#<IfModule ssl_module>
#</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. admin@your-domain.com
#

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
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:/xampp/htdocs"

#
# 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 />
AllowOverride None
Order deny,allow
Deny from 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:/xampp/htdocs">
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
#
# 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
#

#
# 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 All

#
# Controls who can get stuff from this server.
#
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.php index.php4 index.php3 index.cgi index.pl index.html index.htm index.shtml index.phtml
</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,
#
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>
#
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar

#
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
#
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# the filesystem path.

#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
#
ScriptAlias /cgi-bin/ "C:/xampp/cgi-bin/"

</IfModule>

#
# "C:/xampp/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "C:/xampp/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.
#
#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#
#
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#

#
# 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.)
#

# For files that include their own HTTP headers:

# For server-parsed imagemap files:

# For type maps (negotiated resources):

#
# 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.)
#
</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://www.example.com/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
#
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.

# XAMPP specific settings
Include conf/extra/httpd-xampp.conf

# 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

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

<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

Fou-Lu
12-04-2008, 07:26 PM
Is this:

Being striped because of the forums, or is it correct (C:\xampp\php\php5apache2.dll)? I assume thats the correct path as well, you may need to double check the path. Try reversing the \ to / as well, apache may ***** about the windows \'s (my windows apache also uses / and it works without troubles).

Its wierd, it looks like the source is parsing PHP as text, not as php code. The odder part is that the php declaration appears as a comment in the source. And you said this is on a hosted site?

Nblufire12
12-04-2008, 08:18 PM
umm in my config file it has this

is that wrong?

nothing else has full directory path.

Nblufire12
12-04-2008, 09:49 PM
WOW I fixed it...

it was an .HTACCESS file that crashed it for some reason

as soon as i removed it, it worked fine...

Fou-Lu
12-05-2008, 01:40 AM
umm in my config file it has this

is that wrong?

nothing else has full directory path.

No, that was correct. The problem was that the display on the forums here for you're http.conf listed it without the slashes.

WOW I fixed it...

it was an .HTACCESS file that crashed it for some reason

as soon as i removed it, it worked fine...

Great, nothing is more of a pain than this!
This is one of the few problems with allowing configuration changes (with .htaccess) when it comes to software solutions. Its great for customization of specific things, but causes a pain on debugging. I'll file this solution away in the back of my mind in case I see it again.

Nblufire12
12-05-2008, 01:44 AM
Gotya,

you have any tips for home server optimization?

i have 1.5 ghz cpu single core

1.5 gigs of ram

200 gig ATA hard drive

nVidia GeForce 6200

what is the most important part of the computer to make the server faster?

Fou-Lu
12-05-2008, 02:20 AM
Use linux.
Seriously, my old linux box (which is dead now :(), had 32mb of ram. I specifically compiled the kernal as only a webserver, so it was blazingly fast. This was only a year ago (that it died). I'd still be using it if I could afford the hardware (which is now expensive for those ancient machines).

From windows, the only things I can think of is to use fat partitions (saves time since you don't need to lookup permissions), increase priority times, close off any un-used ports, disable un-necessary services, and so forth. Pretty much the same things you'd do on linux.

Depending on you're motherboard, I'd upgrade that old ATA to a SATA and use a dual core processor. That of course would say you had an intel 775 lansocket and sata headers. This is all hardware stuff though and not really meant in this forum.

Unless you're expecting a whole pile of traffic through you're server, you'll be fine with what you have. Its the upload connection that may bottleneck you, so use a DSL connection (or better of course), instead of a LAN unless its super fast. LANS tend to be asyncronous, so you'll get about half the upload versus you're download. Upload is far more important on a webserver. Note, you may be able to contact you're ISP and ask them to either uncap it or reverse it. They'll likely tell you that 'they can't do it', but that's their response to not wanting to provide you with a benefit.

Nblufire12
12-05-2008, 03:04 AM
Use linux.
Seriously, my old linux box (which is dead now :(), had 32mb of ram. I specifically compiled the kernal as only a webserver, so it was blazingly fast. This was only a year ago (that it died). I'd still be using it if I could afford the hardware (which is now expensive for those ancient machines).

From windows, the only things I can think of is to use fat partitions (saves time since you don't need to lookup permissions), increase priority times, close off any un-used ports, disable un-necessary services, and so forth. Pretty much the same things you'd do on linux.

Depending on you're motherboard, I'd upgrade that old ATA to a SATA and use a dual core processor. That of course would say you had an intel 775 lansocket and sata headers. This is all hardware stuff though and not really meant in this forum.

Unless you're expecting a whole pile of traffic through you're server, you'll be fine with what you have. Its the upload connection that may bottleneck you, so use a DSL connection (or better of course), instead of a LAN unless its super fast. LANS tend to be asyncronous, so you'll get about half the upload versus you're download. Upload is far more important on a webserver. Note, you may be able to contact you're ISP and ask them to either uncap it or reverse it. They'll likely tell you that 'they can't do it', but that's their response to not wanting to provide you with a benefit.

haha wow many THANKS

is linux really that much better than windows?

and I use Comcast Cable, will they uncap?

Fou-Lu
12-05-2008, 05:14 AM
Sorry, I was thinking the other way around; DSL is asynchronous and LAN is synchronous. Yeah, that way sounds right. I think >.<
Cable is LAN, so you're up and down should be about the same. Go to speedtester to test that out, just to be certain. As long as you've got about 1MB upload, you're site will serve fine. You're biggest threats with cable are you're bandwidth - too many people on you're node online will result in you're 'lanes' being occupied by their traffic. That, and the technical unlimited bandwidth is definitely not true. We get VDSL here in about 6 more months. 56Mb/s (Where T3 is what.... 45Mb/s) :eek::eek: Sadly, 16Mb/s upload max, stupid Asynchronous technology >.<

Yeah, Linux is that much better. Nix based systems have always had excellent memory handling. Windows is... subpar IMO. At least in a web environment with Apache (which was originally designed for linux). The biggest problem with IIS or windows servers in general with PHP is that it loses thread safety. This is generally not a problem, but every once and awhile you'll notice things like you're timezone change for no reason and then clear up. This would happen with other shared sites, so you won't experience this on a home hosted server.

Don't worry about you're speed, when its just you you'll be fast no matter what you're server is really. Work on securing it instead.

oracleguy
12-05-2008, 06:40 AM
Use linux.
Seriously, my old linux box (which is dead now :(), had 32mb of ram. I specifically compiled the kernal as only a webserver, so it was blazingly fast. This was only a year ago (that it died). I'd still be using it if I could afford the hardware (which is now expensive for those ancient machines).

I know what you mean, my subversion server is a virtual server with only 96MB of RAM that only runs subversion and Apache (I'm using Apache to access SVN). I compiled the kernel and the system software with that in mind so it is pretty lean.

From windows, the only things I can think of is to use fat partitions (saves time since you don't need to lookup permissions), increase priority times, close off any un-used ports, disable un-necessary services, and so forth. Pretty much the same things you'd do on linux.

Depending on you're motherboard, I'd upgrade that old ATA to a SATA and use a dual core processor. That of course would say you had an intel 775 lansocket and sata headers. This is all hardware stuff though and not really meant in this forum.

I would still stick with NTFS with Windows, the permissions can be nice and the file system is a little bit more robust over FAT32. I wouldn't bother really upgrading any of the hardware unless you actually see it being bogged down. You'd be surprised how far that hardware will get you even on Windows when running a web server.

and I use Comcast Cable, will they uncap?

Depending on how much traffic you want to handle and what your current upload bandwidth is, you'd have to upgrade your connection to a more expensive plan to get more upload capability. If you are on the a consumer/home plan you are still bound by your 250GB per month maximum transfer, that includes whatever you upload AFAIK btw.

Nblufire12
12-05-2008, 12:25 PM
ok guys thanks for the info

much appreciated

EDIT

ehh.. www.tindorafarms.com actin up again ??!?!